<Project Name>

Test Plan

Version <1.0>

[Note: The following template is provided for use with the Unified Process for EDUcation. Text enclosed in square brackets and displayed in blue italics (style=InfoBlue) is included to provide guidance to the author and should be deleted before publishing the document. A paragraph entered following this style will automatically be set to normal (style=Body Text).]

[To customize automatic fields (which display a gray background when selected), select File>Properties and replace the Title, Subject and Company fields with the appropriate information for this document. After closing the dialog, automatic fields may be updated throughout the document by selecting Edit>Select All (or Ctrl-A) and pressing F9, or simply click on the field and press F9. This must be done separately for Headers and Footers. Alt-F9 will toggle between displaying the field names and the field contents. See Word help for more information on working with fields.]

Revision History

Date	Version	Description	Author
<dd/mmm/yy>	<x.x>	<details>	<name>

Table of Contents

1. Introduction.. 4

1.2 Background.. 4

1.4 Project Identification.. 4

2. Requirements for Test.. 4

3. Test Strategy.. 5

3.1 Testing Types. 5

3.1.1 Function Testing. 5

3.1.2 User Interface Testing. 5

3.1.3 Data and Database Integrity Testing. 6

3.1.4 Performance Profiling. 6

3.1.5 Load Testing. 7

3.1.6 Stress Testing. 8

3.1.7 Volume Testing. 9

3.1.8 Security and Access Control Testing. 10

3.1.9 Failover / Recovery Testing. 10

3.1.10 Configuration Testing. 12

3.1.11 Installation Testing. 13

4. Resources.. 14

4.1 Workers. 14

4.2 System.. 15

5. Project Milestones.. 16

6. Deliverables.. 16

6.1 Test Model. 16

6.2 Test Logs. 16

6.3 Defect Reports. 16

7. Appendix A: Project Tasks.. 17

Test Plan

1. Introduction

1.1 Purpose

This Test Plan document for the <Project Name> supports the following objectives:

· Identify existing project information and the software components that should be tested

· List the recommended Requirements for Test (high level)

· Recommend and describe the testing strategies to be employed

· Identify the required resources and provide an estimate of the test efforts

· List the deliverable elements of the test project

1.2 Background

[Enter a brief description of the target-of-test (component(s), application, system, etc.) and its goals. Include information such as major function(s) / features, architecture and a brief history of the project. This section should only be about 3 - 5 paragraphs.]

1.3 Scope

[Describe the stages of testing, for example, Unit, Integration, or System, and the types of testing that will be addressed by this plan, such as Function or Performance.]

[Provide a brief list of the target-of-test’s features, functions that will / will not be tested]

[List any assumptions made during the development of this document, which may impact the design, development or implementation of testing]

[List any risks or contingencies that may affect the design, development or implementation of testing]

[List any constraints affect the design, development, or implementation of testing]

1.4 Project Identification

The table below identifies the documentation and availability, used for developing the test plan:

[NOTE: Delete or add items as appropriate.]

Document (and version / date)	Created or Available	Received or Reviewed	Author or Resource	Notes
Requirements Specification	o Yes o No	o Yes o No
Use Case Reports	o Yes o No	o Yes o No
Design Specifications	o Yes o No	o Yes o No
Prototype	o Yes o No	o Yes o No
Users Manuals	o Yes