Re-Testing

Re-Testing is the process of testing the same test cases again to verify that a reported defect has been fixed correctly.

Re-Testing answers: “Is the reported bug really fixed?”

1. Definition

Re-Testing is the process of testing the same test cases again to verify that a reported defect has been fixed correctly.

Re-Testing answers: “Is the reported bug really fixed?”

2. Purpose of Re-Testing

• Confirm defect fixes
• Validate that expected behavior is restored
• Ensure no partial or incorrect fixes
• Provide closure for defect resolution

3. When Re-Testing Is Performed

• After a defect is fixed and a new build is provided
• Before regression testing
• During defect verification cycles

4. Scope of Re-Testing

Re-Testing includes:

• Executing the same test case that failed earlier
• Using the same test data and steps
• Validating expected results

It does not include:

• Testing related features
• Testing side effects (that is regression testing)

5. Re-Testing vs Regression Testing

6. Manual Tester’s Role

• Re-execute failed test cases
• Validate defect status
• Update defect status (Closed / Reopen)
• Provide evidence if defect persists

7. Real-Time Example

Bug: “Submit button not working”

• Developer fixes issue
• Tester re-tests using same steps
• If works → defect closed
• If fails → defect reopened

8. Entry & Exit Criteria (Re-Testing)

Entry Criteria

• Defect marked as fixed
• New build available

Exit Criteria

• Defect verified as fixed or reopened

9. Common Mistakes

• Modifying test cases during re-testing
• Skipping re-testing and directly doing regression
• Using different test data

10. Interview-Ready Answers

Short answer:

Re-testing is the process of executing the same test cases again to verify that a defect has been fixed.

Detailed answer:

Re-testing ensures that a previously reported defect has been resolved by executing the same test steps and validating the expected outcome.

11. Key Takeaway

Re-Testing ensures defect fixes are validated, not assumed.