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

First, the probability of omission

Missing test means that the defects of software products are not found in the testing process, but after the release of the version, users find defects in the process of use.

Second, the significance of preventing missed tests

We all know that the sooner defects are discovered, the lower the cost of finding and resolving them, and much less if they are found in testing. test

It is one of the most important means to ensure the quality of software. therefore, it is very meaningful to carry out missed test analysis, prevent missed test and promote defects to be found as early as possible in the development process.

It helps to reduce the cost of software products and improve the quality of software products.

Third, cause analysis

No one can guarantee that there is nothing wrong with what they are testing, including experienced test engineers, who will more or less let defects slip out of their hands, and no one can.

Think carefully about all the functions and scenarios of the software, but I don't know about old birds like gods.

Causes of missed detection

Corresponding solution

1. The specification of requirements is not clear, which leads to the rough writing of test cases.

1. First carry on the requirement analysis, find out the ambiguity or doubt in the requirement specification, confirm and discuss with the requirement personnel (product), and give a clear definition.

two。 If you find that there is no clear and doubtful point in the testing process, you should also confirm and discuss with the requirements personnel and ask for a clear definition, and then complete the test case.

3. If you can't determine it in time, you can write a general framework first, and then refine and refine the test cases.

two。 Requirements specifications change, test cases are not updated in time

The requirement specification changes, resulting in the original test case does not match the current specification. In the process of executing the test case, if we encounter a place where the test case does not match the specification, we need to record it and supplement and perfect the test case according to the new specification, communicate and confirm with the product or design where there is doubt, we can require a clear definition of the requirement specification, and then organize the new and modified test case into a document and send it to the colleagues in the group to organize review. And update the use cases after the review to the use case base.

3. The test case coverage is not comprehensive, and the scenario is omitted.

Because it is inevitable that test case scenario design leads to defects and omissions, it is impossible for colleagues who write test cases to think through all scenarios, and it is also unrealistic to write all scenarios into test cases. As for the defect of external feedback, it is caused by the incomplete design of the scene. Let's first analyze whether the scene in question is a necessary scenario or an accidental scenario. If the scenario is a customer's operating habit, we can confirm some specific details of the scenario by communicating with the technical interface person. In the process of perfecting the test case, we should also consider some scenarios associated with the scenario. Timely improve and review the test cases in a variety of scenarios and add them to the use case base

4. During the testing process, the test cases are not strictly followed.

We need to face the reality that test cases can not cover all use scenarios, but test cases are written according to requirements and specifications, and have been reviewed by requirements analysis, development, testing and other related personnel. to the maximum extent to ensure the accuracy and comprehensiveness of the use cases. Test cases may not guarantee that all scenarios and function points can be covered, but executing tests strictly according to test cases can ensure the quality of our software to the maximum extent and avoid defects as far as possible. In a word, we should strictly follow the test cases in the testing process, and do not abandon the test cases and test them at will because of the complexity of the test cases. If it is because of random testing in the testing process, resulting in omissions, it really should not be. 5. There is not enough time, resulting in some function points being ignored during testing.

1. Divide the test priority according to the functional module, the main functional module has the highest priority, arrange for experienced people to test, arrange novice to test some unimportant functional modules or rarely used functional modules, in the follow-up testing process, experienced students will test the modules tested by novice to confirm whether there is obvious BUG.

2. Try to avoid wasting your time when it is not clear to the developer. If it takes a long time for the developer to troubleshoot the problem, you can tell the test manager to take corresponding measures to avoid the spread of similar problems through negotiation.

3. Increase the testing manpower

4, work overtime

6. The test environment is limited, resulting in missing defects.

1. Reason: the combination of the environment is infinite, and there is not enough time, manpower, and other resource costs to test in enough environments.

two。 Measures: to ensure the main operating system environment, network environment

Operating system: sorting according to current usage ratio

Network environment: normal network speed, low network speed

7. New BUG introduced by developers

Verify the BUG repaired by the developer and traverse the associated function points to the

Methods: according to the level of developers, choose the appropriate regression testing strategy.

IV. Purpose

No matter what causes the defect to flow to the customer site, the problem occurs, the first thing we need to do is to make up for the impact of the defect, the project team should assess the risks and losses, correct the defect, and provide a perfect version for customers to use. After completing the previous work, we can and even need to consciously think and sum up, draw lessons, and add and improve the problems to the test cases. for some common situations, we also need to learn in the group to avoid making the same mistakes again in the future work.

If we can do a better step, we can learn and make statistics, classify the missing BUG, the severity of the defect, the functional module, the classification of the cause of the omission, and so on. When we carry out defect missing test classification activities, we can organize discussions by special persons. bring together representatives of requirements, development, testing, technical support and other relevant departments in the product life cycle to analyze and discuss recent missed tests, especially technical support personnel can provide a lot of very detailed information about missed defects, which is very helpful to the classification of missed tests, accumulation of experience and lessons learned.

The purpose of defect missing test analysis is to promote the continuous improvement of software quality and development testing process, so that we can be more comprehensive in the testing process and make up for the thinking deadlock. Specifically, through the analysis of the defects in the testing process, some corresponding preventive measures are taken to avoid similar omissions in the future. The continuous improvement of the testing process will improve the effectiveness of the test environment and the efficiency of test execution, reduce the number of defects left to users and the cost of defect resolution, so as to improve the quality of software.

V. Summary

Defect missed detection can not be put an end to, after the occurrence of defect missed detection, we need to learn to think, learn from experience and lessons, as far as possible to reduce the defect missing measurement.

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.