First, what is the test plan

Test scheme refers to the description of the characteristics to be tested, test methods, test environment planning, test tool design and selection, test case design method, test code design scheme.

Second, the role of the test scheme

The test plan is usually divided into internal and external functions. The internal functions are as follows:

(1) As the result of the test plan, let related personnel and developers to review.

(2) Store details of plan execution for peer review by testers.

(3) Store the schedule, test environment and more information.

The external role of the test scheme is to provide customers with a sense of confidence and provide customers with information about the test process, personnel skills, resources, tools used and so on.

background

Provide a brief description of the test objects (components, applications, systems, and so on) and their goals. The information you need to include is key features and capabilities, the architecture of the test object, and a brief history of the project.

Iii. Specific design of test scheme

1. Introduction (including A, writing purpose; B. Intended readers; C, reference materials);

2. Test scope;

3. Test strategy (considering different test methods according to different test types)

Test type: functional test; Compatibility test; Performance test; Interface test; Security and access control testing; Data and database integrity testing; Integration test; User interface testing; Load test; Strength test; Capacity test; Failover and installation testing; Configuration test; Installation test, etc.

1) Functional testing, covering functional modules according to the mind map of requirements analysis and test cases of functional testing;

2) Compatibility test, according to the application scenario of the product, such as IE, Chorme, ios, Android, different models, etc.;

3) Performance test: determine functional interfaces (such as login interfaces) that need to perform performance tests according to product architecture, estimated data and online data;

4) Interface test, security test and so on should be determined according to the actual project requirements. Interface test tool can use domestic interface test and interface document generation tool: APIPost

Fill in the test plan in the form of reference files according to test scenarios, test methods, etc., so that all project personnel clearly know what tests to do and how to do it.

4. Test resources (including A and tester; B. Test environment (test server environment, terminal test environment, network environment); C. Test tools (bug management tools, use case management tools, performance testing tools, etc.); D, bug level definition);

5. Schedule arrangement

1) Test workload estimation: test evaluation (business complexity, test complexity, product quality requirements, number of personnel and ability); Schedule (evaluate the workload of different phases and types of test work, assign manpower, estimate time);

2) Output document: test plan; Functional test cases; Performance test scheme; Bug data; Performance test data; Test reports and so on.

6. Release standards:

1) Test completion criteria: All test types in the test plan have been completed; There are no bugs affecting users in functions and compatibility; Allow a small number of minor bugs to remain, but the number should be less than a value; Performance compliance with design objectives and on-line requirements these standards are for the test work itself.

2) Product release standards: product requirements have been completed; Conform to interactive design specifications, meet visual requirements, design has passed the review; A certain proportion of the remaining small number of bugs have been risk assessed by the project team, which are recognized and the problem is not serious; Product instructions or user manuals or update logs are complete, etc.

7. Risk description

The risk of 1) the test range, such as test requirement analysis is accurate, in place, whether the leakage test points, is missing out on a test type, so the test requirements analysis is the foundation of the whole testing work, as well as the risk of product requirements change, and demand, demand reduction, change requirements need to test requirement analysis;

2) Risks of the test schedule, such as inaccurate workload estimation during planning, resulting in project delay, delayed development work or bug correction, and personnel changes due to more important projects, leave or leave;

3) Risks of product quality, such as the low quality of the developed code or the lack of ability and experience of the testers who are new to the business;

4) Risk of test environment.