"Go" test plan

1. Take full account of the test plan　Practicality, i.e., the proximity and operability between the test plan and the actual. The purpose of the
   writing a test plan is to fully consider the various resources that are performed when testing, including test content, test criteria, time resources, human resources, and so on, to accurately analyze all the resources that can be invoked at execution time, and the various effects that may be affected by various constraints. The point is to "plan" "how" to do "test work" rather than "how to write a test plan".
2. define the scope and content of the test (what), identify the purpose of the test (why), identify the start and end date of the test (when), and explicitly give the test document and the repository location (where); Identify the task assignments of testers (WHO) The method of testing and the test tool (how) are clearly pointed out. "Dmaic model is a set of operating methods for implementing 6sigma"
3. because software projects are a gradual process, demand changes inevitably occur in the middle, and test plans need to be changed in a timely manner to meet changing requirements.　　
   The corresponding review system is to evaluate the completeness, correctness and feasibility of the test plan to ensure the quality of the test.
4. test strategy is an important part of the test plan, which is a macro description of the test requirements of a project, test methods, testers, and other factors, while the test strategy is to explain how the century test process, how to implement the specific. Therefore, the test strategy must be described in detail and focused.

Go to test plan