How to Select regression test cases in software testing

Regression testing is a new round of testing the program after the bug is modified. According to Microsoft statistics, according to their experience
Developer solution 3 ~ Four bugs generate a new bug, which is the reason for regression testing.

The general software testing process is fast iteration in the later stage, and the bug quickly converges in the later stage. The debugging and testing cycle is getting shorter and shorter, and the frequency is getting higher and higher, for example, if the first round of testing takes 10 days to run the test case, it will not take so long in the future, maybe 1 ~ 2 days of testing, sometimes there is a new version in a day later, this time requires
Testers can quickly perform a round of regression testing.

In general, the higher the coverage, the lower the risk, but the lower the efficiency, and vice versa. If time permits, it is best to run all the use cases again, but this time is generally not available. This requires an appropriate balance between efficiency and coverage, select some use cases for regression testing.

In regression testing, efficiency and coverage must be effectively combined. There are usually the following strategies:

• Risk-based selection test:
• What features are software features?
• Which functions are most commonly used by users?
• Which of the following functions will lead to dissatisfaction?
• Which programs are the most complex and error-prone?
• Which programs are most likely to spread errors?
• Which programs are least confident by developers?

Only effective to avoid the biggest risk, the user dislike the problem, the regression test can be said to have reached 70% tasks!

 

Regression testing preferred

 

First, the new function is obviously the focus

Second, the Associated Function of the newly modified function is the coupling part. It is recommended that you consult the developers.

Third, the most selling point or highlights of the program. If there is a problem with this place, it will make the program
High quality discounts

Fourth, the most critical part of the program, for example
Security risks, data leakage, encrypted Registration

Fifth, the fragile part of the program, which should be consulted by developers, is generally the most basic part in their hearts.

Sixth, main functions of the program

7. If there is still time to complete the above steps, it is best to execute the higher-level cases in the case.