A software project test plan is a document that describes the objectives, scope, approach, and focus of a software testing effort. The process of preparing a test plan is a useful way to think through the efforts needed to validate the acceptability of a software product. The completed document will help people outside the test group understand the 'why' and 'how' of product validation. It should be thorough enough to be useful but not so thorough that no one outside the test group will read it. The following are some of the items that might be included in a test plan, depending on the particular project: Title Identification of software including version/release numbers Revision history of document including authors, dates, approvals Table of Contents Purpose of document, intended audience Objective of testing effort Software product overview Relevant related document list, such as requirements, design documents, other test plans, etc. Relevant standards or legal requirements Traceability requirements Relevant naming conventions and identifier conventions Overall software project organization and personnel/contact-info/responsibilties Test organization and personnel/contact-info/responsibilities Assumptions and dependencies Project risk analysis Testing priorities and focus Scope and limitations of testing Test outline - a decomposition of the test approach by test type, feature, functionality, process, system, module, etc. as applicable Outline of data input equivalence classes, boundary value analysis, error classes Test environment - hardware, operating systems, other required software, data configurations, interfaces to other systems Test environment validity analysis - differences between the test and production systems and their impact on test validity. Test environment setup and configuration issues Software migration processes Software CM processes Test data setup requirements Database setup requirements Outline of system-logging/error-logging/other capabilities, and tools such as screen capture software, that will be used to help describe and report bugs Discussion of any specialized software or hardware tools that will be used by testers to help track the cause or source of bugs Test automation - justification and overview Test tools to be used, including versions, patches, etc. Test script/test code maintenance processes and version control Problem tracking and resolution - tools and processes Project test metrics to be used Reporting requirements and testing deliverables Software entrance and exit criteria Initial sanity testing period and criteria Test suspension and restart criteria Personnel allocation Personnel pre-training needs Test site/location Outside test organizations to be utilized and their purpose, responsibilties, deliverables, contact persons, and coordination issues Relevant proprietary, classified, security, and licensing issues. Open issues
什么是软件测试计划？
软件项目的测试计划是描述测试目的、范围、方法和软件测试的重点等的文档。对于验证软件产品的可接受程度编写测试计划文档是一种有用的方式。详细地测试计划可以帮助测试项目组之外的人了解为什么和怎样验证产品。它非常有用但是测试项目组之外的人却很少去读它。依据特定的项目，在一个测试计划中可能包括下面项目：
1、标题
2、软件标识，包括版本/发布版本号
3、目录；
4、文档的目的和阅读人群；
5、测试的对象；
6、软件产品概述；
7、相关文档列表，例如需求规格、设计文档和其它测试计划等；
8、有关的标准和法规；
9、可追溯的需求；
10、有关的命名约定和标识约定；
11、软件项目的相关的所有部门和成员/联系信息/职责；
12、测试项目组和人员/联系信息/职责；
13、假设和依赖；
14、项目风险分析；
15、测试优先级和重点；
16、范围和测试限制；
17、测试描述－根据测试类型、特征、功能、过程、系统、模块等分类；
18、输入等价类分类描述、边界值分析、错误分类；
19、测试环境－软、硬件、操作系统、其它需要的软件、数据配置、与其它系统的接口；
20、测试环境有效性分析－测试环境的不同和产品系统对测试有效性的影响；
21、测试环境建立和配置问题；
22、软件移植性考虑；
23、软件配置管理过程；
24、测试数据建立需求；
25、系统日志描述/错误日志/其它的能力和工具，例如屏幕捕获工具、这对于描述bug和报告bug是很有用的；
26、讨论任何测试人员用来发现bug或跟踪bug的硬件、软件工具；
27、测试自动化－采用的理由和描述；
28、采用的测试工具、包括版本、补丁等；
29、测试脚本/测试代码维护过程和版本控制；
30、跟踪和解决－工具和步骤
31、用于项目的测试度量标准；
32、报告需求和测试交付产品；
33、软件入口和出口标准；
34、初期确定的测试周期和标准；
35、测试暂停和重启标准；
36、人员分配；
37、人员岗前培训；
38、测试地点/场所；
39、测试项目组之外可用的资源和他们的作用、职责、交付、联系人和协调等问题；
40、与所有权相关的级别、分类、安全和许可问题；
41、公开的一些问题。
文章来源于领测软件测试网 https://www.ltesting.net/
