It is a process of re-executing the same test cases in every release just to make sure the new modifications are not affecting the existing functionalities of an application is known as Regression Testing.

Note: Regression testing is a bridge between manual and automation testing.

Characteristics of regression features:

1. The feature which is completely implemented and stable.
2. The feature which is completely defect free.
3. The feature which does not have any change request nearby.
4. The feature which has reached the production.

Q: Do we write test cases for RT?
Ans : No. Instead we use existing test cases from the regression.

Types of Regression Testing :

1. Unit Regression.
2. Regional Regression.
3. Full Regression.

1. Unit Regression:

Some cases the new modifications are not going to affect the existing functionalities of an application. Which is termed as unit Regression.

Example: Spelling mistakes, Alignments etc..

QA Actions:

1. Perform complete smoke testing.
2. Test the new changes.

2. Regional Regression or Risk based testing:

In some cases we can easily predict the affected areas which are due to the new modifications. Hence we take test cases of the impacted regression feature and perform regression testing. which is termed as regional regression.

As in most of the cases the impact areas are predicted/guessed. Hence going by our prediction and performing RT might be a risky approach. But due to the time crunch situations we might go for it.

QA Actions:

1. Perform complete smoke testing
2. Test the new changes
3. Select and execute the impact area regression test cases.

3. Full regression:

In some cases it is very difficult to predict the impact areas caused due to the new modifications. Under such situations we go for full Regression.

QA Actions:

1. Perform complete smoke testing
2. Test the new changes
3. Select and execute all the regression test cases.

Note:  Always do the full regression.

How do you start your automation?

Ans :

• First we will assign the regression test cases to  automation engineers.
• Read or execute, and understand the regression test cases.
• Find out the regression test cases which can be automated.
• Create a POC (Proof of Concept) & give the demo to the team
• If approved, start adding the new test cases.