4.1 Review of learning
Today I mainly learned the preparation of test plans and test summary documents.
1. Test plan
A complete test plan should include:
1. Reasons for writing the test plan
a) Leaders can make macro-controls according to the test plan, carry out corresponding resource allocation, etc.;
b) Testers can understand the entire project testing situation and the requirements of different stages of project testing The work carried out, etc.;
c) It is convenient for other personnel to understand the work content of the tester and carry out related work
. 2. Test process and personnel time arrangement
List the positions, names, and responsibilities of the project participants. Personnel include QA, development, testing, operation and maintenance, etc.
Allocate task scope and time to each person
. 3. Resource environment configuration required for testing,
including software resources and hardware resources
. 4. Testing scope
A) Need to test and pay special attention to which parts of the test:
B) Is the test specifically aimed at solving certain problems:
C) Which parts of the test need to be postponed, and why?
D) Which parts do not need to postpone testing and why?
E) Whether it is necessary to verify the stability of each module:
F) Priority and order of
testing : 5. Test
target items include requirement coverage, test case execution rate, test case pass rate, defect repair rate, defect unrepaired Rate, etc., and set the passing standards.
6. Test risks and constraints
List the risks and constraints that may occur during the test process, and give an evasion plan. For example:
A) The test is not comprehensive due to the objective existing equipment, network and other resource reasons:
B) The test is insufficient due to the on-site customization of the research and development model and the high pressure on the online time:
C) Only for the needs of specific customer groups test:
D) How to deal with the quality of the submitted code and the BUG that cannot be modified in time due to the part-time job of the developer:
7. Test progress
Including date, planning, test system, test content and milestones.
8. Test strategy
Provides recommended methods for testing the test objects. For each test, a test description should be provided and the reasons for its implementation should be provided. What are the main considerations when implementing the test strategy? The technology to be used and the criteria for determining when it will be completed.
Note: If a certain test is not implemented, it should be explained in one sentence, and the reason should be stated, such as: "The test will not be implemented, this test is not applicable to this project"
Explain the basic test process used in the plan, using milestone technology In the testing process, each module is verified. Testers participate in the testing work in the requirement phase, and carry out the required review, design review, test case design and test development. After the system development is completed, the test is formally executed, and the product meets the software product quality requirements and testing. Release after request and submit relevant test documents.
2. Test summary document
After the test process is over, the report document is written.
To be added