22 Difference between Regression Testing and Rest Testing

REGRESSION TESTING:

New functionalities are added to the application
Change Requirement (In organizations, we call it as CR)
Defect Fixing
Performance Issue Fix
Environment change (E.g.. Updating the DB from MySQL to Oracle)

RETESTING:

Build 1.0 was released. Test team found some defects (Defect Id 1.0.1, 1.0.2) and posted.

Build 1.1 was released, now testing the defects 1.0.1 and 1.0.2 in this build is retesting.


Difference between Regression Testing and Rest Testing

1. Regression Testing is performed to make sure the code changes have not affected existing features.

Re-testing is performed to make sure that the test cases which failed earlier are passed after the defects are fixed.

2. Regression testing is carried out to verify whether there is any existing features are affected or not on the basis of new code changes.

Re-testing is carried out on the basis of the Defect fixes.

3. Defect verification won’t fall under regression testing.

Defect verification falls under retesting.

4. Priority of regression testing is lower than retesting. Regression testing is carried out in parallel with retesting.

Priority of retesting is higher than regression testing. Retesting is carried out before Regression testing.

5. We can automate regression test cases. Manual regression testing is more expensive and time consuming.

We cannot automate the test cases for Retesting due to uncertainty.

6. Regression testing is a generic testing.

Re-testing is a planned testing.

7. We do regression testing on passed test cases.

We do retesting only on failed test cases.

8. Regression testing verifies unexpected side effects.

Re-testing verifies whether original defects has been fixed or not.

9. Regression test cases are derived from the functional specification.

Test cases that are failed earlier are used in retesting.