Top 10 principles of software testing

Top 10 principles of software testing The principle is the most important, and the method should be carried out under the guidance of this principle. The basic principle of software testing is to conduct a comprehensive test of the product from the user's perspective, Discover as soon as possible Bug, It is also responsible for tracking and analyzing problems in the product, and raising doubts and suggestions for improvement. Zero-bug) Is an idea, good enough ( Good-Enough ) Is the basic principle of testing. In the software testing process, the specific principles that should be paid attention to and followed can be summarized as ten items:

2. All testing standards are built on user requirements. As we know, the purpose of software testing is to verify product consistency and confirm whether the product meets customer needs, therefore, testers should always look at the problem from the user's perspective and determine the impact of Software defects. The most serious errors in the system are those that causeProgramDefects that cannot meet user requirements.
4. Software testing must be carried out based on the idea of "quality first ".When time conflicts with quality, time must obey quality. Quality philosophy and culture (for example, "do things right for the first time" with zero defects) are also the basis of software testing.
6. Define product quality standards in advance. Only with quality standards can we correctly analyze and evaluate the Product Quality Based on the test results. For example, before performing a performance test, we should define various indicators related to the product performance. Similarly, test cases should determine the expected output results. If the test results cannot be determined, verification cannot be performed.
8. When a software project is started, software testing begins.Instead of starting testing after the program is written. InCodePrior to completion, testers should participate in the requirement analysis, system or program design review, and prepare test plans, test cases, test scripts and test environments, the test plan can start at the completion of the requirement model, and the detailed test case definition can start after the design model is determined. Early and continuous testing should be the motto of testers.
10. It is impossible to perform a exhaustive test.. Even a program of moderate size has a large number of paths. Therefore, it is impossible to run every combination of paths in the test. However, it fully covers the program logic, and ensure that all the conditions used in the program design are possible.
12. Testing by a third party is more objective and effective.Programmers should avoid testing their own programs. In order to achieve the best effect, a third party should conduct testing. Testing is a "picky" behavior, and mental state is an obstacle to testing your own programs. At the same time, it is difficult for the programmer to discover errors caused by understanding the requirement specification.
14. A software testing plan is a prerequisite for software testing.Therefore, a good and practical test plan should be developed and strictly implemented before the actual test, especially the test strategy and test objectives should be determined.
16. Test Cases are designed, not written,Therefore, we need to design test cases according to the purpose of the test, so as to improve the test efficiency, identify more errors, and improve the program reliability. In addition to checking whether the program has done what should be done, it also needs to check whether the program has done what should not be done. In addition to selecting reasonable input data, design test cases for illegal input.
18. Test cases cannot be ignored to avoid randomness.Especially when the modified program is re-tested, if the test case is not strictly executed, a large number of new errors caused by modification errors may be ignored. Therefore, the relevance of regression testing should also attract full attention. A considerable number of final errors are missed in early test results.
20. More in-depth tests should be conducted on the blocks with more errors found.Generally, the more errors found in a program, the higher the probability of errors. The error concentration may be related to the programmer's programming level and habits.