Free Test Plan Template

This is a simple Free Test Plan Template.

Please excuse the formatting - this blog makes it hard to preserve the Word Document formatting I used originally.

---

{ProductName} {Version}
Test / Verification Plan

Revision 1.x
Author: Joe Strazzere

---

Control Page

Title:   {ProductName} {Version} – Test / Verification Plan
File:   {ProductName} {Version} Test Verification Plan.doc
Source Template:
Document Owner:  Joe Strazzere
Date of Issue:  {Date}

Abstract:  This document defines the test verification plan for the
{ProductName} {Version} release. copyrightjoestrazzere

Revision History
Revision Date        Initial      Description
1 mmm dd, yyyy    JSS        Initial document created / sent.
1.1 mmm dd, yyyy JSS         Incorporated suggestions from …

Distribution
Name                                  Role
Firstname Lastname             Project Manager
Firstname Lastname             Engineering Manager
Joe Strazzere                       QA Manager
Firstname Lastname             QA Engineer
Firstname Lastname             QA Engineer

---

Table of Contents

Overview                                                            4
Roles                                                                  5
Platforms                                                            6
Test Environment                                                6
Tracking                                                             7
Release Criteria                                                  8
Categories of Tests                                             9
Approximate Count of Test Cases                      10
References                                                         11

---

Overview

This document will outline the test verification plan for {ProcuctName} {Version}, currently scheduled for Q1 yyyy. 

---

Roles

Following are the relevant major Roles assigned to this project:

 • Project Manager  Firstname Lastname
 • Development Manager  Firstname Lastname
 • Developer   Firstname Lastname
 • Developer   Firstname Lastname
 • Developer   Firstname Lastname
 • QA Manager   Firstname Lastname
 • QA Engineer   Firstname Lastname
 • QA Engineer   Firstname Lastname
 • Doc Manager   Firstname Lastname
 • Configuration Engineer Firstname Lastname

---

Platforms

{ProductName} {Version} will be tested on the following Operating Systems:

 • Windows 2000 Professional (for Proxy Server only)
 • Windows 2000 Server
 • Windows 2003
 • Windows XP Professional

Test Environment
{ProductName} {Version} will be tested in the QA Lab environment, using accounts created for testing purposes.  The following equipment will be used, no new equipment is required:

 machinename1                       machinename2
 CPU Dual 2.4 GHz Xeon      CPU Dual 2.4 GHz Xeon
 2GB RAM                            2GB RAM
 Windows 2003                     Windows 2003

 machinename3                       machinename4
 CPU Dual 2.8 GHz Xeon      CPU Dual 2.4 GHz Xeon
 2GB RAM                            2GB RAM
 Windows 2003                     Windows 2000 Server

---

Tracking

All Requirements, Tests, and Issue Reports will be stored in {BugTrackingSystem} as follows:

 • Database {DatabaseName}
 • Project {ProjectName}
 • Target Ver {Version}

---

Release Criteria

The project will be considered ready for Beta when it meets the following criteria:

 • All functionality has been tested
 • All Issues with Priority=High have been Fixed and Verified
 • In the week before Beta, no new Priority=High Issues are found, despite constant testing pressure

The project will be considered ready for GA when it meets the following criteria:

 • All functionality has been tested
 • All Issues reported from Beta sites have been entered into {BugTrackingSystem}
 • All Issues with Priority=High and Priority=Medium have been Fixed and Verified
 • In the two weeks before GA, no new Priority=High or Priority=Medium Issues are found, despite constant testing pressure

---

Categories of Tests

The following major categories of tests must be performed:

 • New Functionality Tests – The majority of these tests will focus on testing each of the specific new features of {ProductName} {Version}:

  o Support for {NewFeature1}
  o Support for {NewFeature2}
  o Support for {NewFeature3}

 • Integration Testing – Integration testing will verify the interoperability of {ProductName} components.

 • Regression Testing – Regression testing will verify that existing features of {ProductName} continue to operate as expected.

o For {ProductName} {Version}, it will be necessary to perform a full regression testing cycle

 • System Tests – These tests will focus on the {ProductName} product as a whole, single solution in a production-simulated environment.

o Scale, Load and Duration tests will be performed

 • Bug Fix Verification – Throughout the testing cycle, bug fixes will be verified in as timely a manner as possible.


 • Interoperability Testing – These tests will focus on the interoperability of {ProductName} with non-{ProductName} components:

o {OtherProductName1}
o {OtherProductName2}
o {OtherProductName3}
o {OtherProductName4}

---

Approximate Count of Test Cases

Approximately xxx functional Test Cases will be exercised, within the following areas.  More will be added as necessary:

 • {FeatureArea1}   5
 • {FeatureArea2}   35
 • {FeatureArea3}   10
 • {FeatureArea4}   15
 • {FeatureArea5}   20
 • {FeatureArea6}   20
 • {FeatureArea7}   85
 • {FeatureArea8}   5
 • {FeatureArea9}   15
 • {FeatureArea10}   15
 • {FeatureArea11}   25
 • {FeatureArea12}   5

---

References
Version {Version} Requirements

• in {BugTrackingSystem}

{ProductName} {Version} Functional Specification

• In Outlook ({FileNameAndLocation} FunctionalSpec.doc)

{ProductName} {Version} Functional Specification Update (in Outlook)

• In Outlook ({FileNameAndLocation} Functional Specification Update.doc)

{ProductName} {Version} Reference

{ProductName} {Version} Test Developer User Guide

{ProductName} {PriorVersion1} {PriorVersion2} test cases

• in {BugTrackingSystem}