Confirmation testing is performed after a code correction that fixes a reported bug. A tester typically performs the steps required to replicate the defect to verify that the defect no longer exists.

Defects can reoccur in later versions (this may indicate a configuration management problem), which is why confirmation tests are excellent candidates for automation. Automation can reduce the execution time for confirmation tests. The confirmation test can be added to and complement the existing automated regression test bed.

The automated confirmation test typically has a narrow feature set. It can be implemented at any point in time once a failure is reported and the steps required for replication are known. Automated confirmation testing can be integrated into a standard automated regression suite or, where appropriate, incorporated into existing automated tests. Either approach retains the value of automating fault confirmation tests.

Tracking automated confirmation tests provides additional reporting on the time and number of cycles spent resolving defects.

In addition to confirmation testing, regression testing is required to ensure that no new bugs have been introduced as a side effect of bug fixing. An impact analysis may be required to determine the appropriate amount of regression testing.

Source: ISTQB®: CTAL Test Automation Engineer Syllabus Version 1.0