Topic: Regression Testing vs Retesting

Regression Testing
  • Ensures existing features still work after code changes, bug fixes, or enhancements.
  • Focus is on unintended side effects.
  • Usually automated in CI/CD pipelines.
  • Example: After adding a new payment method, regression testing checks that existing checkout, order history, and refunds still work.
Retesting
  • Ensures a specific defect is fixed.
  • Focus is only on the failed test case(s).
  • Typically manual.
  • Example: If a login bug was fixed, retesting verifies that same login case now passes.
Key Differences
Side-by-side comparison of regression testing versus retesting
Feature Regression Testing Retesting
Scope Broad (entire system/modules) Narrow (specific bug fix)
Purpose Catch side effects Verify bug fix
Automation Often automated Mostly manual
Performed on Stable builds Bug fix builds
Test cases Existing plus surrounding areas Failed cases only