Retesting Category

Retesting

Retesting is the process of verifying that previously identified defects have been successfully fixed by the development team. It involves executing the same test cases that initially failed, using the same data and steps, to ensure that the issue no longer exists.

The primary objective of retesting is to confirm that the defect has been resolved as expected without introducing any new issues. It is a focused activity that targets only the specific defects that were reported earlier, rather than testing the entire application.

Retesting is typically performed after receiving a new build or patch where the fixes have been implemented. Each defect is re-evaluated and marked accordingly as Pass (fixed) or Fail (not fixed or partially fixed).

Key Points:

Performed only for failed test cases or reported defects
Ensures that the fix is working as intended
Uses the same environment, steps, and test data as before
Helps maintain product quality and stability
Works closely with defect tracking and validation process

Outcome:

Confirms defect resolution
Updates defect status in the tracking system
Provides confidence in the stability of the fix