Regression Testing

Ques: What is the objective of Regression testing?
Ans: The objective of Regression testing is to test that the fixes have not created any other problems elsewhere. In other words, the objective is to ensure the software has remained intact. A baseline set of data and scripts are maintained and executed, to verify that changes introduced during the release have not "undone" any previous code. Expected results from the baseline are compared to results of the software under test. All discrepancies are highlighted and accounted for, before testing proceeds to the next level.

Ques: Is the Regression testing performed manually?
Ans: It depends on the initial testing approach. If the initial testing approach is manual testing, then, usually the regression testing is performed manually. Conversely, if the initial testing approach is automated testing, then, usually the regression testing is performed by automated testing.

Ques: What do you do during Regression testing?
Ans:
o Rerunning of previously conducted tests.
o Reviewing previously prepared manual procedures.
o Comparing the current test results with the previously executed test results.

Ques: What are the tools available for Regression testing?
Ans: Although the process is simple i.e. the test cases that have been prepared can be used and the expected results are also known, if the process is not automated it can be very time-consuming and tedious operation.

Some of the tools available for regression testing are:
Record and Playback tools – Here the previously executed scripts can be rerun to verify whether the same set of results are obtained. E.g. Rational Robot.

Ques: What are the end goals of Regression testing?
Ans:
o To ensure that the unchanged system segments function properly
o To ensure that the previously prepared manual procedures remain correct after the changes have been made to the application system
o To verify that the data dictionary of data elements that have been changed is correct.

Regression testing as the name suggests is used to test / check the effect of changes made in the code.

Most of the time the testing team is asked to check the last minute changes in the code just before making a release to the client, in this situation the testing team needs to check only the affected areas.

So in short for the regression testing the testing team should get the input from the development team about the nature / amount of change in the fix so that testing team can first check the fix and then the affected areas.