Session-1

Question 1

What is Quality?

Answer 1

Customer satisfaction? Subjective term. It will depend on who the ‘customer’ is. Each type of customer will have their own view on ‘quality’

Question 2

What is Software Quality?

Answer 2

There is two perspective:
1. From consumer perspective it is about customer satisfaction (subjective matter)
2. QA perspective:
· Measurement of how close is actual software product to the expected (intended) product, it is about software being up to requirements.

Quality Software: reasonably bug-free, delivered on time and within budget, meets requirements and/or expectations, and is maintainable

Question 3

What is Software Quality Assurance?

Answer 3

Software QA is the process of monitoring and improving all activities associated with software development, from requirements gathering, design and reviews to coding, testing and implementation.

Question 4

What is the difference between Software Testing and Software QA?

Answer 4

·Testing is mainly an ‘error detection’ process, looks at the source code.
·Software QA is ‘preventative’. It looks at the entire process. It aims to ensure quality in the methods & processes. (“Quality Assurance” is more about the processes involved in producing quality software)

Question 5

What is Software Testing?

Answer 5

Software Testing is the process of analyzing the software in order to detect the differences between existing and required conditions and to evaluate the features of the software. It involves the entire software development process:
- monitoring and improving the process
- making sure that any agreed-upon standards and procedures are followed
- ensuring that problems are found and dealt with, at the earliest possible stage

The purpose of testing is verification, validation and error detection (in order to find and fix the problems)

• Verification is making sure that requirements are implemented. (Verification: Are we building the system right?)
• Validation is making sure that requirements are benefiting the customer.(Validation: Are we building the right system?)
• Error Detection is a sub product of verification: you will find bugs because you verify implementation of requirements not because you looking for a bugs.( finding if things happen when they shouldn’t or things don’t happen when they should.)

Question 6

Is it possible to find/fix all the bugs in a software product before it goes to the customers?
Then – Why test?

Answer 6

No. At least some bugs will be find
QA department working on to establish and to enforce business systems of the QA Organization (Test planning, bug tracking, bug reporting, test automation, release certification, and others)

Question 7

What is black/white box testing?

Answer 7

Testing done from user perspective (software testing is done without access to the source code)
DETAILS:
-Not about WHO does it, but its is about HOW it is done
-Bugs are identified and reported from user perspective
-Could be manual or automated (still black box)

White box testing is done with access to the code. Bugs are reported at the source code level, not behavioral.

Question 8

Describe a bug?

Answer 8

Mismatch between actual behavior of a software application and its intended (expected) behavior. We learn about expected behavior from requirements, specifications, other technical documentation.

Question 9

What is use case?

Answer 9

Use cases are used by Business Analysts as a format for specifying system requirements. A use case is a methodology used in system analysis to identify, clarify, and organize system requirements.Each use case represents completed business operation performed by user. From the QA prospective we would need to execute End-To-End test to make sure the requirement is implemented.

Question 10

What is the most important impact QA can have on a product development process?

Answer 10

· Clarifying requirements

· Bringing down percentage of code re-written due to the change in requirements

Question 11

What is Negative testing? Positive?

Answer 11

· Positive testing aimed at showing software works as intended when user does correct actions.
· Negative testing aimed at showing that software handles properly the situations in which user acts not as user is supposed to act (invalid inputs, unreasonable selections of settings, etc.)
-makes no sense if Positive Testing fails
-negative testing is to be done AFTER positive
-in lack of time situation minimize (skip) Negative Testing
-it results in more bugs than positive

Question 12

Which type of testing results in highest number of bugs found?

Answer 12

Negative

Question 13

What is the software development life cycle?

Answer 13

The software development life cycle (SDLC) is a conceptual model used in project management that describes the stages involved in an information system development project, from an initial feasibility study through maintenance of the completed application.

Question 14

What makes software career attractive to you?

Answer 14

I enjoy working in IT/High Tech environment

• I did the research and it looked like something worth exploring
• I enrolled into QA Training and every day it was giving more confidence
• I am absolutely committed to becoming someone who makes the difference in software testing

Question 15

What is the regression testing?

Answer 15

Partial retesting of a modified program to make sure that no new errors were introduced while making changes to the code (developing new or fixing existing one)
should be done for each new release (build)
we do not have enough time to retest software completely. Risk analysis is involved when we decide on which parts should be tested (partial retesting)
second (to release acceptance) most frequently executed test
very good candidate for automation

AVOID:

• after fixing a bug
• after new feature was added
• making sure the bug was fixed
• not about manual/automated or black/white box

Question 16

What does it take to become a good tester?

Answer 16

James Bach’s comments on my post yesterday considering how a tester can align his perception of himself with reality got me to thinking. What makes a good tester?

The short answer is that I don’t fully know. It will vary a lot based on the project, task, and my current team makeup. However, there are a few things I always look for, and a few red flags. The rest - and there is more - will depend on your project and your team.

So what do I think makes a good tester?
Curiosity. Testing is ultimately seeking information day in and day out. Someone who enjoys seeking out information is going to last a lot longer than someone else.
Detail sifting. A vaguely-worded bug, or feature, or overview of a release’s current status and risk points is worse than useless; it looks like it provides information but it really masks some level of ignorance. Conversely, too much detail creates a problem where you can’t see the actual information because there’s just too much data in the way. A good tester can sift details for relevance and communicate them.
Translation abilities. Usually testers will wind up working with people having very different understandings of the system, different technical facility, and different needs out of a communication event (n.b., fancy speak for “conversation”). A good tester can quickly discern the other party’s focus and skill set, and tailor the conversation to that.
Good memory. I can’t count the number of bugs that I’ve seen found because, “hey, didn’t we try that and see something funny last week?” A good tester will remember what I call the “niggling things”; all those little details that weren’t important at the time, or that we haven’t gotten back to investigating yet. Those niggling details are where your most interesting digging lies.
Logical. If I have to explain every detail of a system to someone, I’m going to go insane (and may take you with me!). I want someone who, given a pattern or a basic understanding, can go figure things out. Further, this tester has an ability to say “if X and Y, then possibly Z”, even without the system actually being in place. This is invaluable in considering the ramifications of a feature change, or thinking about what may have changed in a system due to a configuration change, or considering where we may find bug clusters.
You’ll notice I haven’t said, “Finds a lot of bugs”, or “Has a low duplicate find rate”, or even “Can find the scary issues”. Those things are side effects, not attributes of a person.

So there are lots of wonderful things to look for. What about the red flags?

There are certainly things that scare me:
“I always wanted to do this”. Someone who “always” wanted to be a tester is already prone to exaggeration (at 5 you wanted to be a tester, not, say, a firefighter?). In rare cases that may be true, but it’s more likely that you’ve got someone who’s just trying to appear eager. And I’d rather have truth without exaggeration - what are you going to say when you talk about the system?
“I’m good at finding bugs”. Okay, so you can pick things apart. Finding bugs is part of the job. What about the rest of it? Tell me about that, too.
Automation engineers. I expect all my testers to be able to approach a system with a test mindset. That includes those who will spend most of their time working on test infrastructure/scripts/automation/etc. You still have to be a tester. Note that for this one, I could imagine a situation where this wasn’t a negative, but only in cases where I’m looking to fill a very specific position on a team that has the coverage in other areas.
This is, I suspect, a touchy area. I know that the things I value in a tester are not necessarily the only things - or even the same things - someone else might value in a tester. So let’s hear it: what do you think makes a good tester?

Question 17

what is gray box testing?

Answer 17

Gray box testing is using structural, design, and environment information (complete or incomplete) to expand or focus black box testing and to enhance testing productivity by using appropriate methods and tools.
Extension of BLACK BOX testing

Using methods and tools (languages)

a lot of web testing is done in gray box area

AVOID:
- Combination of black and white box

Question 18

What does it take to become a good tester?
What does it take to start your career in Software QA?
What are the most critical skills of a software tester?
Name one most important characteristic of a good software tester
Who is the best tester: one who finds more bugs or one who gets the most bugs fixed?
Why software quality is not perfect?
Why understanding of SDLC is important to Software QA Engineers?
80/20 rule in application to our online class

Answer 18

The best tester is one who gets the most bugs fixed.