Content ITV PRO
This is Itvedant Content department
REGRESSION TESTING
What is Re-Testing?
Regression Testing is a broad and comprehensive type of software testing performed to verify that existing functionalities continue to work correctly after bug fixes, enhancements, or new feature additions.
Re-testing of Existing Features
Stability Testing
Change-Impact Testing
Regression Testing → Checks the whole system after changes.
Definition
Re-Testing is the process of executing the same failed test cases again after a defect is fixed to ensure the issue has been resolved successfully.
It ensures the particular bug no longer exists.
PURPOSE
Verify Bug Fix
Ensures the reported defect has been fixed properly.
Confirm Expected Behavior
Checks whether the functionality now works as intended.
Improve Product Quality
Prevents reopening of the same defect.
Provide Closure to Defect
Confirms the issue can be marked as “Closed.”
When is Re-Testing Done?
Re-Testing is performed:
-
✅ After a defect is fixed by the developer
-
✅ When a previously failed test case needs verification
-
✅ Before closing the defect in the defect tracking system
-
✅ In every testing cycle where bugs are fixed
Advantages
Confirms Bug Fix
Ensures that the reported defect has been fixed properly.
Improves Software Quality
Prevents the same issue from appearing again.
Increases Customer Confidence
Ensures defects are resolved before release.
Prevents Defect Reopening
Reduces chances of marking a bug as fixed when it is not.
Clear Defect Closure
Helps in properly closing defects in the tracking system.
Time-Consuming (If Many Bugs)
If there are many defects, re-testing each one takes time.
Limited Scope
Focuses only on the fixed defect, not the entire system.
May Miss Side Effects
Does not check whether the fix affected other functionalities.
Repeated Effort
Tester has to execute the same failed test cases again.
Disadvantages
Difference Between Sanity Testing and Regression Testing
| Feature | Regression Testing | Re-Testing |
|---|---|---|
| Definition | Re-testing existing functionalities after changes | Testing a specific defect again after it is fixed |
| Focus | Entire application stability | Specific bug fix verification |
| Scope | Wide | Narrow |
| When Performed | After bug fixes, enhancements, updates | After a defect is fixed |
| Test Cases Used | Previously passed test cases | Previously failed test cases |
| Purpose | Ensure new changes don’t affect old features | Confirm that the defect is resolved |
| Time Required | More | Less |
Example Banking Application
Banking Application
-
A bug was reported: “Incorrect balance displayed after fund transfer.”
-
Developer fixes the issue and provides a new build.
Tester performs re-testing to ensure:
-
Balance calculation is correct
-
Updated balance is displayed properly
-
No incorrect values appear
If everything works fine → Defect is marked Closed.
If the issue still exists → Defect is Reopened.
REGRESSION TESTING
By Content ITV
