Said to the test plan many friend believed to enter this line is no stranger to this, but for a project to do a complete test plan is not so simple, because we are testing before we start on a project, and each project demand analysis, and review and so on a series of preparatory work, so before the test, We need to do a lot of preparatory work to ensure that problems that should be found will not be missed in the test process. Therefore, this article is mainly to explain a set of procedures for the test plan. I hope it will be of some help to colleagues.

I. The purpose of the test plan

(1) Develop a realistic, feasible and comprehensive plan for each test activity, including the object, scope, method, progress and expected results of each test activity. (2) Establish an organizational model for project implementation, and define the responsibilities and work content of each role in the test project. (3) Develop effective test models that can correctly verify the software system under development. (4) Determine the time and resources required for testing to ensure its availability and effectiveness. (5) Establish the criteria for completion and success of each test phase, and the goals to be achieved. (6) Identify various risks in test activities, eliminate possible risks, and reduce the loss caused by risks that cannot be eliminated.

Second, the basic process of test plan

1. Project approval

Project approval is to finalize the project between the user and the project manager, and determine the functions and related responsibilities of the two sides of the project. In this process, the tester is often not involved. In fact, the test manager or team leader can be involved as a participant to understand the relevant matters of the project.

2. Demand analysis stage

In the requirements analysis phase, testers understand the business relationship and analyze the requirement points. Many testers begin their testing work at this stage. Requirements analysis review Reviews the results of project requirements analysis. The review panel shall be determined according to the company’s personnel allocation, generally including users, projects, managers, developers, testers, etc., and shall not be less than 5 members.

3. Test planning phase

Test plan phase: The test leader should start to write the Test plan according to the User Requirements Manual or Test Requirements Analysis Book, including personnel, software and hardware resources, test points, integration sequence, schedule and risk identification. The jury shall be determined according to the company’s personnel allocation, generally including project managers, testers, etc., no less than 5 people.

4. Test design phase

In this stage, a test plan should be proposed for the test work. The test plan is usually planned by a senior test engineer who is familiar with the requirements. The test plan should be designed according to each requirement point in the “Requirement Analysis” and “Test Plan”, including the introduction of the requirement point, the test idea and the detailed test method. The Test Plan also needs to be reviewed after it is written. There shall be no less than 5 judges.

5. Test scheme phase

In this phase, the test is designed in detail, mainly for the design of test cases and procedures. Test cases are written according to the Test scenario, through the test scenario phase, testers have a detailed understanding of the overall system requirements. Start writing use cases at this point to ensure that the use cases are executable and the requirements are covered. Test cases include test items, use case level, preset conditions, operation procedure, and expected result. The operation steps and expected results need to be written in detail and clearly. Test cases should cover test scenarios, which in turn cover test requirement points, so that customer requirements are not missed. Similarly, test cases need to be reviewed. The number of judges should not be less than 5.

6. Test execution phase

Execute test cases, manage execution results, and submit quality bugs in a timely manner.

7. Result analysis and test report

In view of the test results, the tester should analyze the cause of the corresponding results and submit the corresponding test report.