What is Re-Testing?
Retesting is also known as confirmation testing. Retesting is done on the failed test cases with the new build to ensure the defects raised during the software cycle are fixed and work as per the desired specifications. The failed test cases are then re-executed and passed. It is also known as Confirmation Testing.
Example of Re-Testing
Suppose a defect was found in the module “apply coupon/discount” where the discount was not successfully applied to the original price, and now this defect fix is given with the new build. This fix will be re-tested and the corresponding test cases which were failed will be re-executed. This is something known as re-testing.
When to use Re-testing
- It is used to verify the specific bug who fix is provided into the system.
- It is also helpful in confirming the logical reproducible nature of the bug
- It is used to check the quality of any particular feature or module of an application.
Advantages of Re-testing
- It confirms whether the given fix is working for the defect or not.
- It improves the quality of the application or product
- It requires less time for verification because it is limited to testing the specific bug
- It does not require any new environment setup, test data, or test cases. Retesting is done with the same data and the same environment with a new build.
Disadvantages of Re-testing
- A new build needs to be installed to verify the bug fix.
- Sometimes it is difficult to reproduce the same bug due to the unavailability of test cases in some scenarios.
- The test cases for re-testing cannot be automated.
- It requires additional effort and time because of the re-execution of the failed test cases.
- Test cases for Re-testing cannot be obtained before the start of the testing.