Company Name

<Project Name>
<Test Plan Type> End-To-End Test Plan

<PROJECT NAME>
TEST PLAN

[RELEASE X.X

]

TABLE OF CONTENTS

[INSERT TABLE OF CONTENTS]

REVISED: 10/15/08

2

<PROJECT NAME>
TEST PLAN

[RELEASE X.X

]

1

PREFACE

1.1 Created By
[Name of Individual] [Test Team] [Address] [Phone]

1.2 Testing Performed By
[Add appropriate teams.]

1.3 Audience
This document is intended for IT stakeholders including: Environment Support, Development, Analysts, Project Management, Solutions Management, and Product Delivery and Operations. [Add additional teams if appropriate.]

1.4 Who to contact
[Test Lead] [Test Team] [Address] [Phone] [Test Lead’s Manager] [Test Team] [Address] [Phone]

1.5 Revision History
Version [For minor changes use 1.1, 1.2, 1.3 numbering. For major changes use 1, 2, 3, 4 numbering.] Date Last Modified: Modified By: Approved By: [Required if the change was a deviation from the Test Plan.] Notes:

1.6 Document Location
• [Include the link where this document can be found.]

REVISED: 10/15/08

3

<PROJECT NAME>
TEST PLAN

[RELEASE X.X

]

1.7 Related Documents
• • [Include links to folder locations of Use Cases, Test Sets, Process Flows, Interface Agreements, Requirements, and other pertinent documentation.]

2

PURPOSE/SCOPE

2.1

Testing Objectives
[First paragraph should contain the reason for the test effort. Second paragraph should be a cut and pasted definition of the test phase from the Standard Test Approach Document found in the Testing Alignment\Finalized Documentation folder on the Core_Testing vob in ClearCase.]

2.2

Kintana(s) in Scope
• • [List Kintana Number(s).]

2.3

In Scope
• • [List enhancements, interface changes, Tests/Test Sets, systems being tested, and/or any other scope related information.]

2.4

Out of Scope
• • [Optional – Include items that will not be tested.]

3
3.1

AUDIT & CONTROL
Entrance/Exit Criteria

REVISED: 10/15/08

4

<PROJECT NAME>
TEST PLAN

[RELEASE X.X

]

3.2

Success Criteria
[This section will include the basis for the recommendation Testing will make at the end of a phase or release.]

4
4.1

ASSUMPTIONS & CONSTRAINTS
Risk Mitigation Plan
[The complete Risk Mitigation Plan is a separate document from the Test Plan. Provide the document location of the entire Risk Mitigation Plan in this section for reference purposes.]

4.2

Assumptions
1. [Provide a numbered list of all assumptions being made for this Test Plan/Phase.] 2.

5
5.1

ADMINISTRATION
Communication Plan
[Provide information about recurring meetings, daily/weekly status reports, metrics being captured, red status procedures, downtime and critical defect notifications, and other detailed communication information.]

5.2

Roles and Responsibilities
[Include the following information for leads, managers, and other key contacts from all teams: name, role, work phone, cell phone. Also provide a link or the location of the allteam contact list in this section, as this section should only include key contacts.] Name Role Work Phone Cell Phone

5.3

Issue Tracking
[Describe what Issue Tracking tool will be used, including how it will be used and any pertinent information regarding which fields/data should be used for this Test Phase.]

REVISED: 10/15/08

5

<PROJECT NAME>
TEST PLAN

[RELEASE X.X

]

5.4

Defect Tracking
5.4.1 [Name of Tool Being Used] [Include links or document location to bug tracking tool User Guidelines. Include any other pertinent information about the tool being used.] 5.4.2 Defect Severity Guidelines

5.5

Escalation Process
[Use this section to define what types of issues will be escalated, how they will be escalated, and who they will be escalated to.] Type of Issue How to Escalate Who to Escalate To

5.6

Deliverables
• • [List testing deliverables expected from this test effort.]

6
6.1

SCHEDULE
Milestones
[This section will include a list of all of the milestones for the Test Phase. These milestones should closely correspond to the milestones on the Project Plan. If any additional milestones need to be added/deleted for a particular project, they should be added/deleted to both the Project Plan and the list below.] Milestone Hold Kick-Off Meeting Environment Plan Walkthrough & SignOff Environment Setup Complete Automation Environment Setup Complete Data Requirements Complete Automation Data Setup Complete Test Scope Locked Test Plan Walkthrough and Sign-Off Process Flow and/or Functional Design Walkthroughs Complete Test/Test Set Walkthrough and Sign-Off Test Execution Begins Test Execution Completes Planned Date Actual Date

REVISED: 10/15/08

6

<PROJECT NAME>
TEST PLAN

[RELEASE X.X

]

Test Summary Walkthrough and Sign-Off Deployment Lessons Learned Document Complete

6.2

Project Schedule
• [Include a link here to the complete Test Project Schedule.}

6.3

Support Schedule
[Include information on what teams you depend on for support, i.e. Environment Support, Development, Process Analysts, etc.] Team Contact Person Contact Number Hours of Support Link to SLA (if applicable)

6.4

Run & Kitting Schedule

7
7.1

PLAN AND APPROACH
Test Design Approach
[This section should include information on what the tests/test sets are based on (i.e. process flows, design documents, etc.), how they will be written (i.e. joint scripting sessions, teamlets, etc.), and how they will be organized (i.e. by priority, by functionality, etc.).]

7.2

Execution Plan
[This section includes the actual plan for how the tests/test sets will be executed. This will include actual prioritization of scripts, information on when regression and/or automation scripts will be run, and a list of what actual scripts will be run.]

8
8.1

ENVIRONMENT/DATA/CM PLAN
Test Environment Plan 8.1.1 Live Systems Needed
[This section will include a list of all the live systems needed for this test effort. Alternatively, add a link here to the ERD (Environment Requirements Document).] System Needed Team Responsible for Setting Up Environment Date Needed By

REVISED: 10/15/08

7

<PROJECT NAME>
TEST PLAN

[RELEASE X.X

]

8.1.2 List of Stubbed Systems
• • [List any systems that will be stubbed out during the test effort.]

8.1.3 Environment Diagram
[Cut and paste the environment diagram into this section.]

8.1.4 Environment & System Details
[In this section include information on what hardware and software (including versions), operating systems, browsers, and/or platforms you will be using for this test effort. Alternatively, add a link here to the ERD (Environment Requirements Document).] Hardware/Software/OS/Browser/Platfor m Version Number Additional Details

8.2

Test Data Plan 8.2.1 Transactional Data Needed
[This section should include high-level information of what transactional data will be needed at the beginning and throughout the test phase. Include links to more detailed data documentation where applicable.] Transactional Data Needed Date(s) Needed By Who Will Load Data Additional Details

8.2.2 Reference Data Needed
[This section should include high-level information of what reference data will be needed at the beginning and throughout the test phase. Include links to more detailed data documentation where applicable.] Reference Data Needed Date(s) Needed By Who Will Load Data Additional Details

8.2.3 Production Data Needed
[This section should include high-level information of what production data will be needed at the beginning and throughout the test phase. Include links to more detailed data documentation where applicable.] Production Data Needed Date(s) Needed By Who Will Load Data Additional Details

REVISED: 10/15/08

8

<PROJECT NAME>
TEST PLAN

[RELEASE X.X

]

8.3

Configuration Management Plan 8.3.1 Tool(s) Used
[Include information on what tools are being used to manage the configuration of software during the test phase. Also include links to any user guides or other more detailed information on the tools being used.]

8.3.2 Process
[Include information and/or links to documentation on the Configuration Management process that will be followed during this test effort.]

9
9.1

CHANGE MANAGEMENT
Change Request Management
[Describe what change control process is being used at the project level for this test effort. Describe how changes will enter into testing after scope has been locked and provide links to more detailed change control process documentation.]

9.2

Test/Test Set Change Control
[Describe the process that will be followed to change tests/test sets after they have been locked down and are under version control. Include links to detailed process documentation if applicable.]

10

APPROVALS

10.1 Sign-Offs
[One individual from each stakeholder team, as well as the test manager over this test effort, should be included in sign-off.] Stakeholder Name Sign-Off (Yes/No) Date

REVISED: 10/15/08

9