QA Interview Questions
A list of top frequently asked QA Interview Questions or Quality Assurance Interview Questions and answers are given below.
1) What is Quality Assurance?
QA stands Quality Assurance. QA is a set of activities designed to ensure that the developed software meets all the specifications or requirements mentioned in the SRS document.
QA follows the PDCA cycles:
The plan is a phase in Quality Assurance in which the organization determines the processes which are required to build a high-quality software product.
Do is a phase of development and testing the processes.
This phase is used for monitoring the processes and verifies whether these processes meet the user requirements or not.
The Act is a phase for implementing the actions required to improve the processes.
2) What is the difference between Quality Assurance and Software testing?
The following is the list of differences between Quality Assurance and Software testing:
3) How the build and release differ from one another, write down the difference between build and release?
Build is defined as when the software is given to the testing team by the development team.
Release It is defined as when the software is handed over to the users by the tester and developer.
4) Define bug leakage and bug release?
Bug leakage is defined as the bug not found by the testing team but found by the end users. Bug release it is defined when the software is released by the tester in the market knowing that bug is present in the release. These types of bugs have low priority and severity. This type of situation arises when customers want the software on time than the delay in getting the software and the cost involved in correcting the bugs.
5) What are the solutions for the software development problem?
There are five different solutions for the software development problem.
6) Explain the types of documents in Software Quality Assurance?
The following are the types of documents in Software Quality Assurance:
All the functionalities are to be added in the application are documented in terms of Requirements, and the document is known as Requirement document. This Requirement document is made by the collaboration of various people in the project team like developers, testers, Business Analysts, etc.
Test Metrics is a quantitative measure that determines the quality and effectiveness of the testing process.
It defines the strategy which will be applied to test an application, the resources that will be used, the test environment in which testing will be performed, and scheduling of test activities will be done.
A test case is a set of steps, and conditions used at the time of testing. This activity is performed to verify whether all the functionalities of software are working properly or not. There can be various types of test cases such as logical, functional, error, negative test cases, physical test cases, UI test cases, etc.
Traceability matrix is a table that traces and maps the user requirements with test cases. The main aim of Requirement Traceability Matrix is to see that all test cases are covered so that no functionality miss during the software testing.
A test scenario is a collection set of test cases which helps the testing team to determine the positive and negative aspects of a project.
7) What is the rule of a "Test Driven Development"?
In Test Driven Development, test cases are prepared before writing the actual code. It means you have to write the test case before the real development of the application.
Test Driven Development cycle:
8) What is traceability matrix?
Traceability matrix is a document that maps and traces user requirements with test cases. The main aim of Requirement Traceability Matrix is to see that all test cases are covered so that no functionality miss during the software testing.
9) Write down the differences between the responsibilities of QA and programmers?
Differences in responsibilities are as:
Any issue found during the execution of the process by the programmers is communicated to the QA so that they can improve the process.
10) What is the difference between Verification and Validation?
11) Define the key challenges faced during software testing?
The application should be stable for testing.
12) What is the difference between Retesting and Regression testing?
13) Define the role of QA in Software Development?
QA stands for Quality Assurance. QA team persuades the quality by monitoring the whole development process. QA tracks the outcome and adjusting processes to meet the expectation.
Role of Quality Assurance are:
14) Describe the dimensions of the risk in QA?
The dimensions of the risk are:
15) What is the test ware?
Test ware is a term used to describe all the materials used to perform the test. Test ware includes test plans, test cases, test data, and any other items needed to perform and design a test.
16) What is Monkey testing?
There are two types of monkeys:
17) Write the differences between Preventive and Reactive approaches?
Preventive Approach: It is also known as the Verification process. Preventive is the approach to prevent defects. In this approach, tests are designed in its early stages of Software Development Lifecycle before the software has developed. In this approach, testers try to prevent defects in the early stages; it comes under Quality Analysis.
Reactive Approach: It is also known as Validation Process. This approach is to identify defects. In this approach, tests are designed to execute after the software's development. In this approach, we try to find out the defects. It comes under Quality Control.
18) What is the Quality Audit?
An Audit is defined as on-site verification activity, such as inspection or examination, of a processor quality system. Quality Audit is the process of systematic analysis of a quality system carried out by an internal or external quality auditor, or an audit team. Quality Audits are performed at predefined time intervals and ensure that the institution has clearly defined internal system monitoring procedures linked to effective action. Audits are an essential management tool to be used for verifying objective evidence of processes.
19) What is a test plan?
The Test Plan document is a document which contains the plan for all the testing activities to deliver a quality product. The test Plan document is derived from many activities such as product description, SRS, or Use Case documents for all future events of the project. The Test Lead usually prepares it, or Test manager and the focus of the document is to describe what to test, how to test when to test, who will do what test.
20) How do you decide when you have tested enough?
This is one of the most crucial questions. As a project manager or project lead, sometimes we might face a situation to call off the testing to release the product early. In those cases, we have to decide whether the testers have tested the product enough or not.
There are many factors involved in real-time projects to decide when to stop testing:
21) How to design test cases?
There are mainly two techniques to design the test cases:
22) What is adhoc testing?
Adhoc testing is an informal way of testing the software. It does not follow the formal process like requirement documents, test plan, test cases, etc.
Characteristics of adhoc testing are:
23) How is monkey testing different from adhoc testing?
Both monkey testing and adhoc testing follows the informal approach, but in monkey testing, we do not need to have deep knowledge of the software. However, to perform adhoc testing, testers should have a deep knowledge of the software.
24) How is adhoc testing different from exploratory testing?
The following is the list of differences between adhoc testing and exploratory testing:
25) What are the different levels in software testing?
There are four different levels in software testing:
Acceptance testing is performed by the users or customers to check whether it meets their requirements or not.
26) What is a bug life cycle?
The bug life cycle is also known as the defect life cycle. Bug life cycle is a specific set of states that a bug goes through. The number of states that a defect goes through varies from project to project.
When a new defect is logged and posted for the first time, then the status is assigned as New.
Once the bug is posted by the tester, the lead of the tester approves the bug and assigns the bug to the developing team.
The developer starts analyzing and works on the defect fix.
When a developer makes a necessary code changes and verifies the change, then he/she can make the bug status as fixed.
Tester does the retesting of the code at this stage to check whether the defect is fixed by the developer or not and change the status to retest.
If the bug persists even after the developer has fixed the bug, then tester changes the status to Reopen and once again bug goes through the bug life cycle.
The tester retests the bug after it got fixed by the developer if no bug found then it changes the status to Verified.
If the bug is no longer exists, then it changes the status to Closed.
If the defect is repeated twice or the defect corresponds to the same concept of the previous bug, then it changes the status to Duplicate.
If the developer feels that the defect is not a genuine defect, then it changes the status to Rejected.
If the bug is not of higher priority and can be solved in the next release, then the status changes to Deferred.