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、公開的一些問題。
文章來源于領測軟件測試網 http://www.kjueaiud.com/
