Test Plan

<Project Name>

<Authors>

<Date>

<Note: everything surrounded by <> is either a placeholder to be filled in or a comment to be deleted. All tables contain fictional example entries which should be removed.>

<This plan follows the style of IEEE Standard for Software Test Documentation,� IEEE Std 829-1983.>

Table of Contents

• 1 Introduction
• 2 Test Items
• 3 Features To Be Tested
• 4 Features Not To Be Tested
• 5 Approach
• 5.1 Code Inspections
• 5.2 Unit Testing
• 5.3 System Testing
• 5.4 Regression Testing
• 5.5 Acceptance Testing
• 6 Item Pass/Fail Criteria
• 7 Suspension Criteria and Resumption Requirements
• 8 Test Deliverables
• 9 Testing Tasks
• 10 Environmental Needs
• 11 Responsibilities
• 12 Staffing and Training Needs
• 13 Schedule
• 14 Risks and Contingencies
• 15 Approvals
• To Do List
• Revision History

1 Introduction

<Summarize the software items and software features to be tested.>
 

2 Test Items

<Identify the test items including their version/revision level.>
 

3 Features To Be Tested

<Identify all software features to be tested. This may be a list of numbered requirements.>
 

4 Features Not To Be Tested

<Identify all features that will not be tested.>
 

5 Approach

<Describe the overall approach.>

5.1 Code Inspections

5.2 Unit Testing

5.3 System Testing

5.4 Regression Testing

5.5 Acceptance Testing
 

6 Item Pass/Fail Criteria

<Specify the criteria to be used to determine whether each test item has passed or failed testing.>
 

7 Suspension Criteria and Resumption Requirements

<Specify the criteria used to suspend testing, such as abnormal termination. Specify what conditions must be met before testing may be resumed.>
 

8 Test Deliverables

<Identify the deliverable documents, such as this test plan, test specifications, and test results.>
 

9 Testing Tasks

<Identify the set of tasks necessary to prepare for and perform testing.>
 

10 Environmental Needs

<Specify the necessary properties of the test environment, such as hardware and network connectivity.>
 

11 Responsibilities

<Identify the groups responsible for planning, executing, and reporting the results of tests.>
 

12 Staffing and Training Needs

<Specify test staffing needs, such as familiarity with the target operating system.>
 

13 Schedule

<Specify milestones for each type of testing, e.g.., completion of unit testing, completion of system testing.>
 

14 Risks and Contingencies

<Identify the high-risk assumptions of the test plan. Specify mitigation strategies and contingency plans.>
 

15 Approvals

<Specify the names of all persons who must approve this plan.>
 

To Do List

<List of items to be completed in THIS artifact.>
 

#	Who	Due	What
1	Groucho	4/7/2003	Add code inspection plans
2	Zeppo	4/1/2003	Add acceptance test plans

Revision History

Date	Who	Revision
2/2/2003	Groucho	Added regression test plans