Regression testing can be defined as process of testing changes to a programs to make sure that the older programming still works with the new changes.
Regression testing involves reuse of tests to manage risks of change. Usually the regression test is performed by repeating the exact same test as before. But in the case where the test bank is huge and the time allocated is not sufficient regression test should be properly planned ie prioritized. In such cases one should be able to isolate the test cases that are important and may be affected.
The following points can be considered to build the regression test bank:
1. Identiy the modules/functionalities where the bug fixes have been performed. These modules should be tested first as there is a change in the code. You can allocate 50% of your time for testing these modules.
2. Identify the modules/functionalities that are interrelated with the modules where the bug fixes have been done. Perform an Integration test for these modules. This can be allocated 25% of your time.
3. Do a high level smoke test on the rest of the modules. This can be allocated the rest 25% of the time.
The time allocation always differ upon the number of modules to be tested.
This way we will have a good test coverage and also we can ensure that we have performed a good regression testing.
No comments:
Post a Comment