Full Regression Testing

After 2 releases of the product, during the 3^rd release – customer asks for adding 2new features, deleting 1 feature and modifying 1 feature. Also some bugs needed to be fixed. The testing team after doing impact analysis find out that making all the above changes will lead to testing the entire product.

Thus, Testing the changes and all the remaining features is called Full Regression Testing.

When do we do Full Regression Testing ?

®     When changes are more

®     Whenever the changes are done in the root of the product. For ex, JVM is the root of Java application. Whenever any changes are made in JVM, the entire Java application is tested.

Regional Regression Testing is the most preferred method of regression testing. But the problem is, we may miss a lot of bugs doing Regional Regression Testing.

We can solve this problem by the following method – when a product is given for testing, for the 1^st ten cycles, we do regional regression testing, then for the 11^th cycle, we do FRT. Again, for the next 10 cycles, we do RRT and for the 21^st cycle we do FRT. Thus we continue like this, for the last ten cycles of the release – we do only FRT. Thus, following the above method – we can catch a lot of bugs.

Disadvantages of doing regression testing manually again and again,

·         Monotonous job

·         Efficiency drops down

·         Test execution time is more

·         No consistency in test execution

Thus, we go for Automation to solve this problem. When we have more cycles of Regression testing – we go for Automation.

Automation :

Customer gives requirements – we start writing test cases – about 1000test cases are written for the entire product – development team gives the 1^st build – we convert about 600 test cases to QTP scripts and the remaining 400 test cases are not converted – we executed the converted QTP test cases using QTP tool. Remaining 400, we test manually – thus 60% of time is saved by automating our testing.

 Disadvantages of doing regression testing manually again and again,

·         Monotonous job

·         Efficiency drops down

·         Test execution time is more

·         No consistency in test execution

Thus, we go for Automation to solve this problem. When we have more cycles of Regression testing – we go for Automation.

Automation :

Customer gives requirements – we start writing test cases – about 1000test cases are written for the entire product – development team gives the 1^st build – we convert about 600 test cases to QTP scripts and the remaining 400 test cases are not converted – we executed the converted QTP test cases using QTP tool. Remaining 400, we test manually – thus 60% of time is saved by automating our testing.

QTP stands for Quick Test Professional