Regression Testing

Testing of the modified, new functionality or corrected code to check that the updated code is not breaking anything which was working earlier.

It is a common practice for the companies to change their code due to couple of reasons. There could be a new enhanced version or correction of logged defects. In all the cases, a proper regression testing is required. It gives confidence to the stakeholders that there is no broken functionality due to the changes or correction of the code.

It is recommended to automate the set of testcases that are tested manually and gained confidence. Though it is demands lot of expertise and time, still automation of the testsuite saves a lot of time in the future whenever you have to run a regression testing.

Benefits of regression testing

  • Helps in identifying side defects that may seep in during fixing of logged defects
  • Increase Chances of detecting bugs due to changes in the new code
  • Helps and ensure high quality of the product
  • Overall increase the stakeholders’ confidence in the product

 

How we do it at SeerTechnologies.

There are various types of Regression testing practiced at SeerTechnologies, however, it depends upon few factors like type of changes introduced, bugs fixing, functionality changes, requirement enhancement etc.

 

 

Corrective Regression Testing

This type of regression is used when there are no changes made in the requirement specification. There could be defect fixing only in or around a module. Only a small no of testcases can be reused for the regression testing.

 

 

Retest-all Regression Testing

It involves testing of all new aspects as well as reusing all the old testcases. Usually, it is recommended when there are many changes and involving more than 1 module. Consider the same when there are changes in the product’s specification.

 


Selective Regression Testing

It is done to check the impact of new code addition to the already existing product. A subset of the old testcases can be reused and reduce the efforts. Usually, a dot version is released with the new changes.

 


Progressive regression Testing

When there are certain changes done in the requirements as well as new testcases are also designed. With the new testcases, a subset of old testcases is also run. The selection of the testcases depends upon the integration of the new functionality with the existing one. We need to identify all the paths where new features would impact.

 


Complete Regression Testing

A complete regression testing is done when there are multiple changes in the whole product. A new version would be pushed to the production in such cases. It requires a complete testing of the product with new testcases as well as reusing the old major testcases . In case, the version is rectifying any defects, those subsets of the testcases also need to be run.

 

 

The main aim of the Regression Testing is to find out the side effects due to changes or error fixing, hence maintaining a high product quality. This definitely demands to keep a separate budget in terms of time, resource and money. Do not overlook its importance.

Follow us onFacebooktwitterlinkedininstagram
Share the postFacebooktwitterlinkedin
Quick Connect