"Fundamentals of Software Testing"-[5]. Software Testing Principles

all test software testing should be traced back to the user's needs

This is because the purpose of software testing is to use the user to complete the scheduled tasks, and meet the needs of users, and software testing revealed defects and errors in the software can not reach the user's goal, not meet the needs of users. "Early and continuous software testing" should be used as the motto of software Testers

Test requirements run through the entire software lifecycle, and the cost of fixing defects increases with each stage. From the usual eye-catching, it has been seen that the demand phase introduced by the bug is not less than the design stage, how to ensure that the stable and effective demand is very important. a complete test is impossible, the test needs to be terminated

That is, zero bug and good enough; What this article has taught us is a standard of test execution. It is impossible to reach 0bug by any test. Then we should reach good enough. This principle is a tradeoff between input/output ratio: testing is neither sufficient nor possible, we need to develop tests to solve the above problems through standards and test content, such as: Number of bugs Left & severity, test case execution Rate & pass rate, etc. Software testing does not show potential defects in software

Testing can be done to find and report the software defects and errors found, but there is no guarantee that the software defects and errors can all be found, continue to be a test may find some, that is, the test can only prove that the software has errors and cannot prove that the software is not error. pay attention to the cluster phenomenon in testing

That is, the 80-20 principle, the main thing to tell us is the defect cluster phenomenon, the more defects found in the module will need to devote more human energy to test. programmers should avoid checking their own programs

For testing purposes, it should be tested by an objective, impartial, and rigorous independent testing department or an independent third-party testing facility. try to avoid the randomness of the test

Develop a rigorous test plan and schedule the test as loosely as possible, with organized, planned, and step-up testing activities. the relevance of regression testing

The relevance of regression testing must be paid full attention. It is not uncommon to modify an error to cause more errors to occur. Focus on what the program shouldn't do

Check what the program should do, which is just half of the testing effort, and the other half of the testing effort is the ability to check what is not supposed to be done.

Description: Most of the content is reproduced from: Software Testing principles-Wu Zhuyan