There are a lot of testing terminologies present that are used at various stages of a product under testing. Confirmation testing helps to determine the quality of the product as well as its components. In this article, we are going to discuss confirmation testing.
What is confirmation testing?
Confirmation testing is a type of software testing technique used by testers to check if the previously posted bugs are rectified or not in the system or its components. Confirmation Testing is also known as retesting.
Example – Let’s say a product is developed by the development team and now goes through the testing activities performed by testers. The testing team found some bugs (Bug1 and Bug2) and posted them for rectification to the development team. The product will be checked again after the development either accept the bug and rectifies it with a new build or rejects the bug.
Features of Confirmation testing
- Confirmation testing is performed before regression testing.
- The scope of confirmation testing is clear and unchangeable.
- Confirmation testing is planned to test.
- Tests cases cannot be automated.
- Can be performed with the help of old test cases, so there is no need to create new test cases.
When is confirmation testing done?
- When a particular bug is fixed with a new build
The testing team ensures that the previous bug which was posted is fixed by the development team with the new build.
- When a particular bug is rejected
Sometimes the development team rejects the bug reported by testers and indicates the status of a bug as not reproducible. In this situation, testers need to do a retesting to verify that the particular bug is valid and reproducible.
- Before Regression Testing
Sometimes the changes done in the product do not appear with the new build of the product. Thus, re-testing is done as it mainly focuses on verifying and rectifying the defects.
- When the client requires a re-testing
At times to be sure of the product quality, the client can ask the testing team to do the confirmation testing again and again.
What to do after confirmation testing is done?
As the confirmation testing is completed, the next step is to proceed with regression testing in which we check that the previous build of software or product remains unaffected with the addition of new features or functionalities to the product.
Advantages of Confirmation Testing
- Confirms the quality and functionality of the product.
- No need to create any new environment setup.
- Guarantees that no issues are present in the product when it reaches the end-users.
Disadvantages of Confirmation Testing
- Additional time and effort are required in the re-execution of the failed test cases.
- We cannot automate the test cases for retesting.
- The new build is required for defect verification.
With the above article, we can understand the importance of confirmation testing and that it can be done at all levels of testing.