How to compile a test plan

As the saying goes: everything goes wrong. Software testing also requires the development of corresponding testing plans at the beginning of the testing project. Next we will discuss how to compile the test plan.

 

I. First, I want to know the following questions:

 

1. Why write a test plan?

1) The lead is able to make macro adjustments and configure corresponding resources according to the test plan;

2) The tester shall be able to understand the entire project test and the work to be carried out at different stages of the project test;

3) Facilitate related personnel to understand the work of testers and cooperate with them

2. When will the test plan be written?

(Overall test plan before testing requirement analysis/detailed test plan after testing requirement analysis)

3. Who will write the test plan?

Experienced project testing Director

4. What are the six elements of the test plan? (5w1h)

1) why -- why do we need to perform these tests;

2) What-test what aspects and work content of different stages;

3) When-test the start and end times of different stages;

4) where-relevant documents, defect storage location, test environment, etc;

5) who-project personnel, who are arranged for testing

6) How-how to perform the test and what testing tools and methods are used for the test.

 

Ii. Main content of the test plan:

 

1. Introduction

1.1 Project Background

1.2 References (Basis for plan preparation: Feasibility Analysis Report/software requirement definition/software Outline Design/software detailed design/user manual /......)

1.3 Test term

1.4 Project personnel composition and contact information (developers/version control personnel/testers/software, hardware, structure, and marketing personnel)

2. Task Overview

2.1 test Scope

2.2 test objectives

2.3 In a broad sense, it also includes test requirement analysis, test case writing, test environment setup, test training, and test execution.

3. Test Strategy

3.1 tester requirements and division of labor

3.2 testing methods (Automated/manual testing; white box testing/black box testing; interrupt testing/critical testing/stress testing)

3.3 tool reference and test training (internal/external training)

3.4 testing phase plan (work content, staffing, start and end times, etc)

3.5 test stop and recovery Conditions

3.6 Test Documents and defect submission Management

3.7 test environment

4.Test Resources

4.1 hardware resource requirements

4.2 software Resource requirements

4.3 test environment requirements

4.4 tester requirements

4.5 others (instruments, servers, etc)

5.Risk Assessment

5.1 manpower;

5.2 time;

5.3 environmental aspects;

5.4 Resource

5.5 departmental cooperation

6. Other content

In addition to the above content, it also includes testing plan makers, dates, modification records, reviewers (developers/test owners/project managers) and other information

 

Iii. Notes for preparing test plans

 

1. the test plan does not have to be perfect, but must be realistic. It should be prepared based on the project characteristics and the actual situation of the company;

2. once a test plan is developed, it is not just a layer of change. Everything in the world is changing all the time, and software requirements, software development, and staff flow are constantly changing, the test plan should also be adjusted based on actual changes to meet the actual test requirements.

3. the test plan should reflect the test tasks, test stages, and resource requirements of the project from a macro perspective. It may not be too detailed.

 

Iv. Review Summary

 

1. Plan Review

After the test plan is prepared, it is generally necessary to review the correctness, comprehensiveness and feasibility of the test plan. The review personnel should be composed of software developers, marketing personnel, test owners and other relevant project owners.

2. Plan Summary

After the project is completed, the implementation of the Plan should be reviewed to see what is unreasonable, so as to accumulate experience in preparing the next project test plan.

This article is shared with you at http://www.cnblogs.com/itest/archive/2008/06/24/1229151.html!