Risk-based testing)

From: http://www.microsoft.com/china/CTC/Newsletter/06/ctc2.htm

The risk of software products can be calculated by the severity of errors and the probability of occurrence. Tests can determine the testing priority and test coverage based on different risk levels.

Risk analysis process
. List all features and features of the software
. Determine the possibility of failure for each function
. What is the impact on customers if a feature fails or lacks a feature?
. Calculate risk
. Modify the risk level based on indications of possible errors.
Determine the scope of the test and compile the test plan.

From: Microsoft

Risk-based testing refers to the evaluation of the test priority. A high-priority test is performed first. If time or energy is insufficient, a low-priority test can be performed temporarily. As shown in the following figure, the horizontal axis represents the impact, and the vertical axis represents the probability. It is determined based on the characteristics of a software: If a function has a problem, how much impact it has on the entire product, what is the probability of a failure in this function? If there is a high probability of a problem and the problem has a great impact on the entire product, it must be covered during testing. For a feature rarely used by a user, the probability of a problem is very small, and the impact of the problem is not very great. If the time is tight, you can consider not to test it.