1.1 Test Plan

A good test plan is used to plan the test and to guide the entire test process. is a description of the manpower, time, resources, strategy, scope of the entire test process.

The three elements of the core are time, resources, and scope.

Time is when and how long it takes, resources are the human, machine, and other resources you want to invoke, ranging from what you want to test and the focus of your testing.

In addition to the above mentioned 3, there are more important items such as strategy (how to measure), risk control (once there is a problem to take any contingency measures) and other projects.

To make a plan very practical, according to the author's experience, pay attention to the following aspects:
A. Time, resources, scope three elements can not be less
B. Test strategies must be clear, that is, how to test
C. Need for coordination of other personnel (departments), to clarify
D. When estimating the time, manpower and other resources required for testing, be objective, accurate, and open, especially when estimating development time and debug time, and to speed up your own execution cases.
E. Each phase of the test plan should be clearly indicated, and the input and output documents of the test phase should be clearly
F. The time period in the test plan should not be too long (preferably in day), too long is more vague, bad measurement, bad check
G. Must have risk control, otherwise the plan lacks enforceability
H. After completion of the plan is not installed in the pocket, to organize PM and development for review
I. To keep the plan up to date, keep in mind that every plan is dynamic, not immutable.

20160704 Summary:

(ZK) should be asked clearly at the initial project meeting

1. The test environment, operating platform, etc. required for the project.

hardware environment such as computer model, CPU, memory.

software environments such as browser compatibility (IE, chrome, Firefox, etc.), operating system compatibility (Win7, win8, WIN10, etc.).

network environment such as a network (2G, 3G, 4G, WiFi, Mobile telecommunications unicom), no network, inferior network

Above, need Luo to list

2. Required test Strategies: interface testing, automated testing, functional testing, integration testing, security testing, performance testing, etc. (Development unit tests)

* Reference: http://blog.csdn.net/inc143/article/details/2433163 (several test plan templates)

3. Milestones such as test resource allocation, expected project development completion time, delivery time (customer acceptance test), end time (final delivery), etc.

PS: The temporary template is as follows

Test Total work:
Test analysis time, TC writing time, smoke test time, functional test first round, first round regression, main process regression test
Test Manager to manage hours, project risk (new technical difficulties, etc.), review meeting (Requirements review, TC review)

It is expected that the development classmate Xxxx.yy.zz test.
Expected to test classmate Xxxx.yy.zz complete the test, xxxx.yy.zz on-line. If the development self-test and smoke testing are passed, then the development of formal survey;
Develop formal test time for test students to start testing time.
If development cannot be measured on time, the project team decides that the corresponding test activity will be postponed or considered overtime.

The test plan needs to be sent to the corresponding development, testing, requirements, business, development boss, Test boss, etc.

1.1 Test Plan