Shulou(Shulou.com)06/03 Report--

When writing a test plan, consider the risks that may occur and propose countermeasures. So what are the risks to pay attention to? How to solve the problem? Some scenarios are listed below:

Design:

Risk: (1) there is no detailed design specification

Solution: testers should analyze the relevant design and requirements documents in the development phase, classify the general module functions, analyze business logic, and communicate with developers in time where they are not clear.

Risk: (2) there is no unified interface design specification.

Solution: confirm the test standards with the project leader.

Development:

Risks: (1) there is no unified design for all module development, and developers have their own design methods.

Solution: confirm the standard way with the project leader, and all areas that are inconsistent with the standard way are submitted in BUG form.

Risk: (2) requirement change development.

Solution: it is recommended that the requirements changes be documented, and the requirements changes without documentation should be confirmed with the developer in time during the testing process, and the relevant change documents should be archived.

The test itself:

Risk: (1) Human resources

Solution: ensure a stable staffing arrangement.

Risk: (2) hardware resources

Solution: analyze the hardware resources needed for testing in advance and apply in time to ensure that the testing work is carried out smoothly.

Risk: (3) version control

Solution: the version is strictly controlled and BUG is submitted on a version-by-version basis. Any code updates are prohibited during testing and during the BUG confirmation phase.

Risk: (4) insufficient testing time.

Solution: mobilize testers to complete the testing tasks and, if necessary, give corresponding material rewards.

Testing risk is inevitable and always exists, so the management of testing risk is very important. We must try our best to reduce the risk in testing, maximize the quality and meet the needs of customers. In testing, the main risks are:

First, the quality requirements or the characteristics of the product are not understood accurately, resulting in errors in the analysis of the test range, resulting in some places that cannot be tested or the standards verified are incorrect.

Second, the test cases have not been 100% executed, such as some test cases have been intentionally or unintentionally omitted

Third, temporary / sudden changes in requirements, resulting in design changes and code rewriting, insufficient testing time

Fourth, the quality standards are not all very clear, such as the applicability of the test, the benevolent see benevolence, the wise see wisdom

Fifth, the test case design is not in place, ignoring some boundary conditions, deep logic, user scenarios and so on.

6. the test environment is generally impossible to be completely consistent with the actual operating environment, resulting in errors in the test results.

7. Some defects occur with a frequency of not 100% and are not easy to be found. If the code quality is poor and there are many software defects, there is a great possibility of defects being missed.

Eighth, regression testing generally does not run all test cases, which is selectively executed, which inevitably brings risks.

The first three risks are avoidable, while the four risks of four to seven are unavoidable and can be minimized. The last risk of regression testing can be avoided, but it generally exists for the sake of time or cost.

In view of the risks of the above software testing, there are some effective testing risk control methods, such as:

The test environment is not correct by listing all the items to be checked in advance, and after the test environment is set up, other people can check them one by one according to the listed items.

The consequences of some test risks can be so serious that they can be converted into other low risks that will not cause serious consequences. For example, on the eve of product release, a serious defect is found on a new function that is not very important, and if this defect is corrected, it is likely to cause a defect in the original function. At this time, the risk of dealing with this defect is very great, and the countermeasure is to remove the new function and transfer the risk.

Some risks are inevitable, so try to reduce them. For example, the risk of "defects not found in the program" is always there. We have to reduce this risk by increasing the coverage of test cases (such as 99.9%).

In order to avoid, transfer or reduce risks, risk management plans and risk control strategies should be made in advance, and some emergency and effective solutions should be made to deal with the risks, such as:

When making estimates of resources, time, cost, etc., you should leave some leeway and do not use 100%.

Before the start of the project, include factors that may change and are difficult to control on the links or boundaries into the risk management plan.

Train reserve personnel for each key technical personnel, prepare for personnel mobility, and take some measures to ensure that once the personnel leave the company, the project will not be seriously affected and can continue.

Develop document standards and establish a mechanism to ensure that documents are produced in time

Review all work and find problems in time, including exchanging different testers on different test modules

Follow up all the processes on a daily basis, find the signs of the risk in time, and avoid the risk.

In order to really avoid risks, we must completely change the management mode of the test project, and establish a management consciousness of "prevention" or "prevention-oriented" in view of the various risks of the test. Compared with the traditional software testing, the whole process test management method can not only effectively reduce the product quality risk, but also avoid the software product defects in advance, shorten the defect feedback cycle and the testing cycle of the whole project.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.