Regression testing and Retesting in software testing

Regression Testing

• It is type of testing carried out to ensure that changes made in the fixes or any enhancement changes are not impacting the previously working functionality.
• It is executed after enhancement or defect fixes in the software or its environment. It can be difficult to determine how much re-testing is needed, especially near the end of the development cycle.
• Every time after making changing in the existing working code, a suite of test case have to executed to ensure that changes are not breaking working features and not introduced any bugs in the software. It is essential to prepare such test suite & executed on every newer version of software. Also to automate the regression testing this test suite will help to create an automated testing script.

     In regression testing, tester has to do only the execution of previously executed test cases & compare the result with previously test execution result. If there is not conflict between results then we can say that the regression testing is passed.

    In this type of testing new test cases are not created but previously created test suite is executed to find regression defects.

    But if you are testing GUI applications the doing regression testing is very difficult. If the changes made in the GUI then all test cases written will not reused. In case if the project is big then it is very hectic work to update the GUI test cases. You have to write it again different test case for updated GUI once again.

Retesting:

Retesting is done to make sure that bug is fixed and failed functionality is working fine or not, This is kind of verification method followed in testing field for the fixed bugs.

Sl.No	Regression Testing	Retesting
1	It is re-execution of the test cases for unchanged part to see that unchanged functionality is working fine are not.	It is done to make sure that bug is fixed and failed functionality is working fine or not, This is kind of verification method followed in testing field for the fixed bugs.
2	Retesting is a planned testing	Regression is known as the generic testing.
3	Defect verification is not come under Regression testing.	Defect verification is comes under Retesting.
4	Based on availability resources the Regression testing can be carried out parallel with Resting.	Priority of Retesting over Regression testing is higher, so it is carried out before Regression testing
5	Automation is the key for Regression testing. Regression testing is right time to start automating test cases.	We cannot automate the test cases for Retesting
6	In Regression testing we can include the test cases which are passed earlier.	In Retesting, We can include the test cases which are failed earlier and we can say that check the functionality which was failed in earlier build.

Note: We should always keep this in mind, Re-testing has higher priority than the regression testing. But in bigger projects Retesting and Regression is done in parallel effort. But never forget importance of both in the success of the project.

Enjoy testing! If you like it above Testing related information then please kindly take a moment to share with your friends. You can add your suggestions/tips/questions below in the comments section. Definitely, I will try to answer of all questions as earliest. 


You may also like:
Complete Testing Material

Testing basic interview questions