Retesting And Regression Testing

Regression testing:

Regression testing is actually done “to not regret at later stages for the failure of developed software”. Regression testing is a type of software testing to confirm that recent changes to the program or code should not adversely affect the existing feature.

Suppose the testing team has reported a bug and developers team has fixed that bug by modifying the code and pass it for testing, now the regression testing is performed to verify that the changes which were performed to fix the bug should not have any side-effect on existing functionality of the software, if the bug is raised again then it passes again to developers team.

                                In IT world regression means “return of bug”.

When to perform regression testing?

1. To fix the performance issue.

2. When a new feature is added to the software.

3. To provide a good quality software.

Regression test cycle


 

The above figure represents the regression testing cycle which actually shows how the regression testing is done, here we have three test cases.

In first cycle all these three test cases are executed, test case A and C are passed and test case B gets fail then a bug is raised which will pass to the developer's team. When the bug gets fixed and second cycle starts then regression testing is performed with already designed test cases.

In the second cycle only the test case A gets passed and other two test cases get failed, by doing this we can see that after fixing the bug associated with test case B, it has lead to the failure of test case B and C, so regression test cycle is repeated until we get the software free of bugs according to our test suite which is executed.

Retesting

Retesting means  “ Testing again”.

Retesting is a type of software testing that is performed to verify  an application

Once again after  the bug has been fixed.

In this, the test cases which were failed previously are executed again.

When to perform retesting?

• When we have to test only the specific functionality or to verify the Previously fixed bug is actually fixed or not.