Testing_124 : Retesting and Regression Testing

After fixing the issues of 1.0v of application and completed coding of 2.0v. Developer sends 2.0v for testing.
So Tester will test 2.0v of application and retest the defects of 1.0v. For Checking the integration of the application 2.0v with 1.0v, tester have to test the whole application. For this situation we used automation testing tools.

Retesting and Regression Testing :-

What is Retesting ?

Retesting of the application to verify whether defects have been fixed or not.

What is Regression Testing ?

• It is Re-execution of some or all test cases of a testing activity for each build to verify that changes or fixes made have not introduced new errors.
• Regression testing is done in two situations. ONE is after fixing the bug and SECOND one is if a new change request will come from client. Here we have to verify whether already existing functionality can getting defects.
• Regression testing is one type of retest, where we can retest the application after bug fixes or any new functionality is added.

Release 2.0 execution process :-

Step 1 : After receiving release 2.0 from development team, as a QA we need to perform smoke testing.

Step 2 : Understand the release note documents and perform re-testing for the fixed defects (if any).

Step 3 : After Re-testing, the defect status should be updated in tracking tool and also prepare a retesting report and send to management.

Step 4 : As per the release note document based on new functionality, perform the functionality testing, by executing test cases.

Step 5 : After completion of new functionality testing, then perform regression testing based on old releases.

Retesting Template :-

Retesting Reporting Example :-

For Detail on Execution Process Click on link : Release wise Execution Process