Re Testing and Regression Testing | Difference
Re-testing or confirmation testing is testing a defect fix to confirm that the original defect has been successfully removed.
After a defect has been fixed, re-testing is performed in software testing to check the scenario under the same environmental conditions.
During Re-testing, testers look for minute details at the changed area of functionality.
Regression testing is the repeated testing of an already tested program, after modification, to discover any defects introduced or uncovered as a result of the change.
Some Features of Regression Testing:
- The extent of regression testing is based on the risk of not finding defects in software
- was working previously.Impact analysis should be performed to determine the extent.
- Tests should be repeatable.
- Regression testing may be performed at all test levels, and includes functional, nonfunctional and structural testing.
- Regression testing is a strong candidate for automation.
Regression testing is performed when:
- New functionalities introduced
- Change Requirements
- Defect Fixing
- Performance Issue Fix
- Environment change
Difference between Re Testing and Regression Testing (Re Testing vs Regression Testing)
Re Testing | Regression Testing |
Re-Test means confirmation of something | Regression means the return of a bug.  |
It is done once the defect is fixed | Done whenever there is a change in code |
Should be performed before regression testing | Can be done parallel with retesting |
Can’t be automated | Should be automated |
Re-tests are planned | Regression tests are considered a generic test. |
Retesting is carried out to ensure that the original issue is working as expected. | Regression testing is carried out to check for unexpected side effects. |
Defect verification is coming under Retesting. | Defect verification doesn’t fall under Regression testing. |