1.

 Why Should We Hire You?

A favorite question for interviewers from all over the world. This isn’t a trick question –
it’s an icebreaker.

Answer: Take this opportunity to put your strongest foot forward. Talk about what
makes you passionate about QA testing, why you’ll do the job better than anyone else
due to the unique combination of talent and personality traits that only you can bring to
the role. Don’t worry about being self-critical or overly humble here. The question is
designed to talk about the strengths of the applicant. 

This question is so often mentioned in interviews that entire columns have been written
to put minds at ease. If you’re still feeling like you need more guidance on how to
answer this question, I recommend checking out BigInterview’s comprehensive
article for further advice.

2. What is a Bug?

Answer: A bug is any kind of error, mistake or failure in software code that prevent the
software function from executing properly. 

3. What is the difference between severity and

priority?

Answer: These are important distinctions that must be known for proper time
management. Severity is how difficult the issue is to fix. Priority is how important the
issue is to fix. 

Just because an issue is high severity doesn’t necessarily mean it’s high priority and
vise versa.

Here’s an example of a high severity, low priority issue:

The application crashes when a rarely used function is run on legacy software
that most users can’t access.

Here’s an example of a low severity, high priority issue:

 The wrong company logo is displayed on startup. 

4. What is the difference between Assert and Verify

commands in test automation?

Answer:  There is a lot of similarity between the two commands. Both check if the codes
conditions are true. The difference is what happens next.

When an assert command fails it will stop executing code and the test will pause.
When a verify command fails it will plow ahead and execute the rest of the code.

5. What is the difference between Quality Assurance,

Quality Control and testing?

Answer: Quality assurance plans the way in which test process will be monitored within
a team and organization. Quality control finds defects and suggests ways to improve
the software. Testing is the process in which quality assurance and quality control find
bugs

6. When Should QA start?

Answer: QA should begin as soon as possible. The earlier QA analysts, testers and leads
get involved in the process the more headaches are being prevented later in the
development cycle. Static tests can be performed before the software is fully
functional. 

7. What is the QA Testing Life Cycle?

Answer:

1. Requirements
2. Planning 
3. Analysis 
4. Design 
5. Implementation 
 6. Execution 
7. Conclusion 
8. Closure 

 8. What is a test plan? 

Answer: A test plan is a document that outlines the details of the intended test. It states
before testing begins the required roles, potential risks and solutions, and resources it
will use.

9. What does a test plan include?

Answer: Test plans should include:

The scope,
The approach
Resources required
Intended schedule of the test/s 

10. What is a Use case?

Answer: Use cases describe the cause and effect of a function. It makes sure that the
user action and the system response are talking to each other properly. 

 11. What is a Test Strategy?

Answer: The test strategy outlines the plan for the testing stage of software
development. Unlike the test plan, which describes one specific test, the test strategy
covers the entire testing phase of development and includes a description of the testing
tools, test groups, test priorities, test record maintenance, and the test summary. 

12. Are Test Strategies and Test Plans the Same

Document?
Answer: No. Test plans collect and organize test cases.

Test strategies describe the approach towards testing. In general, test strategies are
managed by the QA manager or QA lead while test plans are managed by the QA
testers.

 13. What are some different kinds of testing?

Answer: Regression testing, exploratory testing, functional testing, integration testing,

unit testing, white box testing, black-box testing, alpha testing, and beta testing. For
more on different testing techniques, check out our post on software testing.

14. What is a good test case?

Answer: A good test case clearly states the parameters in which the test will be
performed and the bugs it hopes to find. 

15. What is the difference between functional and

nonfunctional testing?

Answer: Functional testing tests the key parts of the software to ensure it matches
requirements and specifications. Nonfunctional testing tests important but not crucial
aspects of the software such as load times, stress and overall performance. 

16. Should QA’s resolve production issues?

Answer: Yes. It’s often good for the QA to be involved in solving production issues. They
should, when possible, write test cases and try to find the issues. By getting involved,
the QA is minimizing the number issues in the final product.

17. When You Find a Bug in Production, How Do You

Ensure That The Bug Gets Resolved? 
Answer: The best course of action is to immediately write a test case for the bug and
run a regression test. That way any future tests performed on the software should
check specifically for that bug.