First, the test program
1 Overview
Documentation purposes, test background, the scope of the definition of terms, reference
2, test purposes
3, the test range
Functional test coverage, test coverage interfaces, data accuracy, performance testing range
4, testing resources
Environmental testing requirements, test plans, human resources division
5, test constraints
Test out conditions, the test pass and fail criteria, test start / stop / pause / restart guidelines
Release agreement, the test defect management, defect tracking modification process standards process standards, defects
6, functional test programs
Test tools, test program needs assessment, test type (smoke, functions, processes, boundary value, fault tolerance, start and stop, install, compatible, easy to use interface, interface, configuration, security, performance, regression, document test), testing strategy (data extraction, the platform functions, user interface, compatibility testing, interface testing, performance testing)
7, test execution management strategy
8, test risk analysis
9, test output
10, the demand for change control
Second, the test report
Third, the demand for change control
1. Change conditions
1) In the test planning stage, if the system requirements are subject to change and the demand has been developed, you can simply change the demand, if the demand has not yet developed, the development of new testing requirements according to system requirements after the change;
2) if the following conditions may be changing requirements:
ü test planning phase has been completed, testing requirements has been confirmed and signed;
ü test execution phase has not yet started;
3) If the test execution phase appears the system requirements change, and the changes to the system has little effect, you can fill in the memo recording, make changes in the next test project;
4) If the test execution phase appears the system requirements change, but the change must be greater impact on changes to the system, then the test is responsible for staff and customers to be reached on this recognition, and fill in the memo, and then execute demand change process. If you need to pause or suspend execution of the current test, you need to change the protocol and correct test plan.
2. Change Process
1) To change request, the person in charge to fill the demand side "testing needs change notice" and submit the appropriate information to change the person in charge of testing parties;
2) Test side analysts test requirements change;
3) Change the demand side of the person in charge of changing needs Review and confirm completion;
4) After the change to confirm, modify or re-testers to write test cases;
After using the new test test test.