Regression testing strategy

When selecting a regression testing strategy, we need to take both efficiency and efficiency into account. We can do our work in the following two aspects:

1. Maintenance of the test case Library:
Delete outdated Test Cases
Improve uncontrolled test cases (for some test cases that are very sensitive to input or running states, the test is not repeated and the results are difficult to control, which affects the efficiency of regression testing and needs to be improved, make it meet repetitive and controllable requirements)
Delete redundant/repeated test cases
Add/supplement new test cases

2. Regression test solution selection:
A. test all the use cases again (the method is safe, but the implementation cost is too high, which is generally used less)
B. Test the selection based on risks (select the most important, most common, and risky function for testing)
C. Select a test based on the Operation Section

(If the test cases in the baseline test case library are developed based on the software operation section, the distribution of test cases reflects the actual usage of the system. The number of test cases used in regression testing can be determined by the test budget. regression testing gives priority to the test cases that are most important or frequently used to release and mitigate the highest level of risks, it helps to identify faults that have the greatest impact on reliability as soon as possible. This method can improve the system reliability most effectively under a given budget, but it is difficult to implement it)

D. Test the modified part again.

Combined with actual work conditions, the most common problems are: D + A combination (verify the problems solved by the current version first, and then verify the most important, common, and risky use cases)

 

The basic process of regression testing:
1. Confirm the modified part of the software (Follow up the changes and test comments provided by the Bug Management System );
2. From the original baseline test case library, select the corresponding test case (basic) to create a new test baseline.
3. If there is a test case change (delete or change) or a demand change (Add a new requirement), first update the test case and then start the test.

Notes for regression testing:
1. All versions of the current version must be restored to avoid leaving errors in the next test version;
2. During the regression test, the software version should be frozen. If problems found in the regression test are not resolved or the problems are not solved, the software version can be returned based on the company's actual situation.

Regression testing strategy