Introduction
Retesting is an important activity in software testing performed after a defect has been fixed. It ensures that the reported bug has been successfully resolved.
What is Retesting?
Retesting is the process of executing the same test case again to verify that a specific defect has been fixed. It focuses only on validating the corrected functionality.
Retesting is different from regression testing because it targets specific defects.
Why Retesting is Important
- Confirms defect resolution
- Ensures quality improvement
- Prevents reopening of issues
- Improves customer satisfaction
Retesting Process
- Developer fixes defect
- QA receives updated build
- Execute failed test case
- Verify defect is fixed
- Close or reopen bug
Retesting vs Regression Testing
- Retesting: Verifies specific bug fixes.
- Regression Testing: Verifies overall system stability after changes.
- Scope: Retesting is narrow; Regression is broad.
- Test Cases: Retesting uses failed test cases; Regression uses full test suite.
Real-World Examples
Example 1: Login Issue
- Bug: User unable to login with valid credentials
- Developer fixes issue
- Tester re-executes login test case
- If successful → Bug closed
Example 2: Payment Failure
- Bug: Payment confirmation not displayed
- Tester retests only payment confirmation scenario
Advantages of Retesting
- Ensures accurate defect resolution
- Improves system reliability
- Maintains software quality
- Reduces recurring defects
Retesting Interview Questions
What is retesting?
Retesting is executing failed test cases again to verify bug fixes.
Is retesting part of regression testing?
No, retesting focuses only on specific defect validation.
When is retesting performed?
After developer fixes a reported defect.
Frequently Asked Questions
Can retesting be automated?
Yes, repetitive defect validation scenarios can be automated.
Who performs retesting?
QA testers perform retesting before closing defects.