As the saying goes: Everything pre-standing, not pre-waste! Software Testing in the same way, at the beginning of the test project to develop a corresponding test plan . Next talk about how to write a test plan.
A Here are a few things to know first:
1. Why write a test plan?
1) The leader can do macro-adjustment according to the test plan, and allocate the corresponding resources;
2) The tester can understand the whole project test situation and the work of the project test at different stages;
3) to facilitate other personnel to understand the work of the testers, to carry out relevant work
2. When do you start writing a test plan?
(Test requirements analysis before the overall test plan/test requirements analysis after the detailed test plan)
3. Who will write the test plan?
Experienced Project Test leader
4. Test Plan write 6 elements? (5W1H)
1) why--Why these tests are carried out;
2) what-test which aspects, different stages of the work content;
3) when-test the starting and ending time of different stages;
4) where-corresponding documents, storage location of defects, test environment, etc.
5) who-The personnel of the project, and arrange which testers to test
6) How to do how-, what test tools and test methods are used to test.
Two Test Plan main content:
1. Introduction
1. 1 Project Background
1. 2 references (Plan preparation basis: Feasibility analysis report/software requirement definition/software outline design/software detail design/user manual/...) )
1. 3 Testing Terminology
1. 4 Project personnel composition and contact information (Developer/version control/testers/software, hard, structure, marketing personnel, etc.)
2. Task overview
2. 1 Test Range
2. 2 Test target
2. 3 in broad sense also includes test requirements analysis/test case writing/test environment build/test training/test execution, etc.
3. Test strategy
3. 1 Test personnel requirements, Division of labor
3. 2 test methods ( Automated test /manual test; white box test / black box test ; interrupt test/Critical test/stress test, etc.)
3. 3 tool Reference and test training (internal training/foreign training)
3. 4 Test phase plan (Job content, staffing, start/end time, etc.)
3. 5 test stop and restore conditions
3. 6 test document and defect submission management, etc.
3. 7 test environment
4. Test resources
4. 1 Hardware Resource requirements
4. 2 Software Resource requirements
4. 3 Test Environment requirements
4. 4 Test personnel requirements
4. 5 Other (instruments, servers, etc.)
5. Risk assessment
5. 1 human aspects;
5. 2 time aspect;
5. 3 environmental aspects;
5. 4 Resource aspects
5. 5 Sectoral cooperation
6. Other content
In addition to the above related items, but also include the Test planner, date, modification records, reviewers (development leader/test Lead/project manager) and other information
Three Considerations for writing Test plans:
1. Test plans do not have to be perfect, but must be realistic, according to the characteristics of the project, the company's actual situation to compile, can not be divorced from the actual situation;
2. Once the test plan is formulated, it is not a layer of constant, the world everything is constantly changing, software requirements, software development, personnel flow and so on at a time of change, test plan also according to the actual situation changes and continuously adjust to meet the actual test requirements.
3. The test plan should be able to reflect the project's test task, test phase and resource requirement from the macro level, not necessarily too detailed.
Four Review summary
1. Program Review
After the completion of the test plan, the test plan will generally be the correctness, comprehensiveness and feasibility of the review, the composition of the reviewers include software developers, marketers, test leaders and other relevant project leaders.
2. Plan Summary
After the completion of the project, the implementation of the plan should be reviewed to see what is unreasonable, in order to prepare the next project test plan to do experience accumulation.
Five Test Plan Template (sample)
......
How to write a test plan