编写测试计划的目的

To prescribe the scope, approach, resources, and schedule of the testing activities. To identify the items being tested, the features to be tested, the testing tasks to be performed, the personnel responsible for each task, and the risks associated with the plan.
- IEEE Standard 829-1998
 
定义测试的范围、测试的方法、所需的资源、进度等，明确需要测试的产品项，需要覆盖的功能特性，需要执行的测试任务，每项任务的负责人，识别相关的风险。
 
IEEE 829所定义的测试计划大纲如下：
a) Test plan identifer;
b) Introduction;
c) Test items;
d) Features to be tested;
e) Features not to be tested;
f) Approach;
g) Item pass/fail criteria;
h) Suspension criteria and resumption requirements;
i) Test deliverables;
j) Testing tasks;
k) Environmental needs;
l) Responsibilities;
m) Staffing and training needs;
n) Schedule;
o) Risks and contingencies;
p) Approvals.
 
The test plan is a by-product of the detailed planning process that's undertaken to create it. It's the planning process that matters, not the resulting document.
测试计划是详细的计划过程中的一个副产品。重要的是计划的过程，而不是文档本身。
 
The ultimate goal of the test planning process is communicating (not recording) the software test team's intent, its expectations, and its understanding of the testing that's to be performed.
测试计划的最终目标是表达（而非记录）测试组的意图、期望，以及他们对于即将进行的测试的理解。