What is Regression Testing?

- Regression means retesting the unchanged parts of the application. Test cases are re-executed in order to check whether previous functionality of application is working fine and new changes have not introduced any new bugs. This test can be performed on a new build when there is significant change in original functionality or even a single bug fix.


- This is the method of verification. Verifying that the bugs are fixed and the newly added features have not created in problem in previous working version of software. Testers perform functional testing when new build is available for verification. Regression test should be the part of release cycle and must be considered in test estimation.

- Regression testing is usually performed after verification of changes or new functionality. But this is not the case always. For the release taking months to complete, regression tests must be incorporated in the daily test cycle. For weekly releases regression tests can be performed when functional testing is over for the changes.

- Regression testing is actually a test suite that is supposed to test as much functionality of your application as possible.

Example for your application. You have separated test suite for 5 levels as below:
P1 – P5 (Smoke -> Full Functional Test)

•      P1 – Smoke Test

•      P2 – Partial Regression Test

•      P3 – Full Regression Test

•      P4 – Partial Functional Test 

•      P5 – Full Functional Test 

P1	P2	P3	P4	P5
Collect smoke test cases and execute them everyday	Partial Regression Test to collect key test cases and execute two times over one week	Full regression test to execute test suite on last Friday of two week over one month	It is executed as part of + Manifest analysis (if any) + 1/month on last Friday of the month	Are test cases of stable modules or UI test cases, CMS  related test cases, link verification - are executed as part of + Manifest analysis (if any) + 1/quarter on last Friday of the quarter

•      

 

HoaLe