Confirmation Testing

What is meant by confirmation testing?

Let us consider, a software product has been developed by the development team, and now it needs to go through the testing activities for its quality check. After the execution of the tests, some defects were found in the software that needs to be fixed or resolved. After applying corrections to the software product, it is required, to check whether the defects, that were explored, got fixed or not. This situation, then calls for the confirmation testing.

Confirmation testing or Re-testing, is all about testing the software product, again to check that whether all the previous bugs found has been resolved or not.

In this type of testing, test cases that were effective in detecting the defects in the software product, are again applied over it, after the fixation of the bugs. This is done, to ensure that the software product which was not able to pass the test cases, is now able to pass these test cases after applying corrections in the software product in order to remove bugs.

Is Confirmation testing = Regression testing…??

No, Confirmation testing is different from the regression testing. In regression testing, it is checked that the modifications introduced in the software product in order to remove the bugs does not affect the existing functionality of the software product, whereas confirmation testing is concerned with the re-testing the software application, to check that the bugs or defects, found during the previously performed testing has been removed or fixed.

Key Points:

  • Also known by the name of re-testing, it is done to ensure that the bugs have been removed or fixed, which were found during the testing.
  • Generally, test cases which are responsible for exploring the defects in the software product are used in the confirmation testing to validate that the software is bug-free, under the same conditions and environment.
  • It is different from regression testing. Further, on priority basis, confirmation testing comes before the regression i.e. re-testing activity may be followed by the regression testing.
  • The scope of re-testing is unpredictable and could not be determined, especially, near to the end of the development process.
  • Automation may prove to be useful, for carrying out the testing process, with the help of automation testing tools.