retesting

Retesting is the process of re-executing a defined set of test cases that previously failed due to a defect, after the defect has been fixed in the codebase. The goal is to verify that the specific defect is no longer reproducible and that the fix works as intended.

Retesting is distinct from regression testing. Retesting focuses on the fixed defects and the immediate areas of the code that were changed, while regression testing checks that recent changes have not introduced new issues elsewhere in the software.

When to perform retesting: after a developer applies a fix and a new build is available, and when a defect ID and expected outcome are documented. Retesting typically occurs as part of the bug-fix verification cycle, often before a release or a formal closure of the defect.

Process: identify the original failing test cases, re-run those test cases with the same inputs and environment, and observe results. If the test passes, the defect is considered fixed and the test case is marked as retest passed. If it fails, the defect is reopened and investigated, and additional testing may be required.

Scope and preparation: retesting usually covers only the area affected by the fix, not unrelated functionality. Good practice includes linking test cases to defect IDs, and using the same test environment and build as the original failure.

Automation: retesting can be manual or automated. Automated retests can speed verification for critical defects and enable frequent execution.

Benefits and limitations: retesting confirms that a specific fix works and reduces release risk, but it does not guarantee the absence of new defects elsewhere. It should be complemented by broader regression testing.