HomeTesting Concepts

What is Re-testing?

What is Re-testing?
Re-testing is a type of testing which is performed to verify whether the defects reported earlier are fixed by the developer. Go through the following points, to further understand the Re-testing in detail:
  • Re-testing is performed on the newer builds having bug fixes, to verify whether the bugs reported earlier are fixed in the newly provided build.
  • As part of Re-testing, the test cases which are failed earlier due to the reported bugs will be retested.
  • Re-testing is also performed by testers on the bugs which are not reproducible by the developers, to confirm the reproducibility of the earlier reported bugs.
  • Re-testing is also known as Confirmation Testing
  • Re-testing is carried out before the Regression testing is performed.
  • In Re-testing, we not only verify the fixed defects on the newly provided builds, we also verify the functionality to which these fixed defects belongs.
  • As part of Re-testing, the same test data and steps will be used to verify the reproducibility of the earlier reported defects in the newly provided build.

Re-testing versus Regression Testing: The following points will help you in understanding the difference between Re-testing and Regression testing:
  • Regression Testing: Regression Testing is a type of testing which is generally performed to ensures any enhancements or bug fixes or new additions in the software code, has not introduced any side effects into the previously working software. Here unchanged functionality in the application will be verified to ensure that there are no side effects due to the code changes in other functionalities.
  • Re-testing: Re-testing is performed on the newer builds having bug fixes, to verify whether the bugs reported earlier are fixed in the newly provided build. Here the test cases of the functionality for which the code changes have been made for fixing the defects will be verified.

Re-testing flow: The following is how the Re-testing is performed on the fixed defects in real time:
  • Step # 1:  Testers will verify the application and report defects to the developers
  • Step # 2:  Developers will fix the defects reported by developers and provide them with a new build having defect fixes for testing
  • Step # 3: As part of Re-testing, Testers will re-run the failed test cases to ensure the earlier reported defects are fixed.

Conclusion: Re-testing is performed to ensure whether the earlier reported defect is fixed in the newly provided build.

Please leave your questions/comments/feedback below.

Happy Learning 🙂

Arun Motoori (www.QAFox.com)

Comments (0)

Leave a Reply

Your email address will not be published. Required fields are marked *