Project Number

Project Name

<Test Phase> Test Plan

Version N.N
Version Date: MM/DD/CCYY

Author: First Name Last Name

<Company Logo>
 <Company Logo>
Project Number, Name, Release
ITPR0nnnnn Project Name

Revision History

Version Date Name Changes

N.N MM/DD/CCYY Initial test plan

Disclaimer:
Any screen mockups in this document are for visualization purposes only. The final user
interface look and feel may vary based on decisions made in the design and
development phase. No change request or defect will be created if the screens
delivered do not exactly match the mockup as long as the requirements documented are
met and the screen development standards are followed.

Test Plan <Company> Proprietary and Confidential Page 2 of 8

 <Company Logo>
Project Number, Name, Release
ITPR0nnnnn Project Name

Table of Contents
Test Plan ............................................................................................................... 4
1 Purpose ......................................................................................................... 4
2 Objectives ...................................................................................................... 4
3 Scope ............................................................................................................ 4
4 Roles and Responsibilities ............................................................................. 4
5 Assumptions and Dependencies ................................................................... 5
6 Risks .............................................................................................................. 5
7 Test Strategy ................................................................................................. 5
8 Entrance and Exit Criteria .............................................................................. 7
9 Required Deliverables ................................................................................... 7

Test Plan <Company> Proprietary and Confidential Page 3 of 8

 <Company Logo>
Project Number, Name, Release
ITPR0nnnnn Project Name

Test Plan
1 Purpose
The purpose of this document is to plan, prepare and implement the test effort for
the <Project Name> project. The test phase, roles and responsibilities, testing
procedures and test environment are all discussed in this plan.

<Project summary>

2 Objectives
Define the scope, approach, resources and schedule
Communicate the test strategies to all responsible parties
Define the activities required to prepare for and execute testing
Communicate the planned tasks, coverage and test requirements

3 Scope

In Scope
<Will testing affect multiple applications or platforms?>
<What features will be tested? (refrain from a technical breakdown of the
system)>

Out-of-Scope
<Will any features be excluded? Why?>
<Will any platforms or systems be excluded? Why?>

4 Roles and Responsibilities

Task Name
Develop test plan and obtain approvals <Name>

Create test cases and obtain approvals <Name>

Prepare/identify test data <Name>

Test Plan <Company> Proprietary and Confidential Page 4 of 8

 <Company Logo>
Project Number, Name, Release
ITPR0nnnnn Project Name

Task Name

Execute test cases, document results, obtain approvals <Name>

Approve <test phase> test plan, test cases and test <Name>
results

Testing will begin on <start date> and be completed by <end date>.

5 Assumptions and Dependencies

<Identify significant constraints such as test item availability, resource availability,
tools, schedule, etc.>

End-to-end, functional, system, integration, regression and/or performance

testing will be conducted independently from <test phase>
All defects opened during QA will be closed prior to starting <test phase>
IT and QA resources will be available to support beta testing as needed
IT will resolve defects and address issues as they are raised
System resources will be available

6 Risks
<Identify high-risk issues and the contingency/response for each.>
Tight timeframe to execute <test phase>. Start planning early to prevent any
issues that may result in delays during the <test phase>.
Access to test environment is dependent on authorization cycle time. Confirm
tester access to test environment early and, if needed, request access in
advance, monitor progress and escalate if needed.

7 Test Strategy
Test cases will be documented in an Excel workbook and executed within the pre-
defined schedule.

Test Environment and Tools

<Test phase> will be conducted in the <environment> environment

Test Plan <Company> Proprietary and Confidential Page 5 of 8

 <Company Logo>
Project Number, Name, Release
ITPR0nnnnn Project Name

Testers will have the necessary tools, login credentials and authority to access
the test environment.
<Is there a project characteristic that requires a special testing tool?>

Test Data
The <test phase> team will use production-like setups for the following active and
inactive data.
<Identify project-specific setups>

Test Execution
Testers will complete all assigned test cases within the pre-defined timeframe
specified by the Project Manager.
Testers will execute assigned test cases provided in the Test Case workbook
and capture each test result in the Test Results document.
Testers will categorize each test case as Pass or Fail in the Test Case
workbook.
Testers will document a failed test case in a Word document. Defect
documentation will include the test case ID, test case description, expected
result, actual result and screen shot of the defect or issue. The document will
<Test phase> is considered complete when 100% of the cases have been
successfully tested.
A successfully completed test case is one that produces the expected result;
i.e., when valid data produces the expected outcome or invalid data produces
the expected error message(s).

Defect Management
Testers will document the test case ID, test case description, expected result,
actual result and screen shot of each defect or issue and forward the document
to test support
Test support will open the defect in Quality Center or forward the issue to the
appropriate person for clarification
IT will notify the <test phase> team when a fix is available for retest
Testers will retest fixes and categorize the test results as Pass or Fail

Test Plan <Company> Proprietary and Confidential Page 6 of 8

 <Company Logo>
Project Number, Name, Release
ITPR0nnnnn Project Name

<Test Phse> Schedule

Task Start End

Test plan <mmddccyy> <mmddccyy>
Test cases and test data <mmddccyy> <mmddccyy>
Test execution, review and approval <mmddccyy> <mmddccyy>
<Test phase> end <mmddccyy> <mmddccyy>

8 Entrance and Exit Criteria

<Test Phase> Entry Criteria

QA testing completed and approved

All defects opened by QA are fixed, retested and closed
<Test phase> test cases are complete and ready for execution

<Test Phase> Exit Criteria

All planned tests have been executed
All test cases pass expected results
All identified defects have been addressed

9 Required Deliverables

<Test Phase> Artifacts

<Test phase> deliverables and other project documents are stored on the project
SharePoint site at: <SharePoint link>
Test Plan
Test Cases
Test Results

Approvals
Electronic signatures will be captured using Outlook voting buttons and stored in
the SharePoint site common drive.

Test Plan <Company> Proprietary and Confidential Page 7 of 8

 <Company Logo>
Project Number, Name, Release
ITPR0nnnnn Project Name

Test Plan completion/approval is required prior to the start of <test phase>.

Role Name

Role 1
Role 2

Interested Parties
Name
Name
Name

Test Plan <Company> Proprietary and Confidential Page 8 of 8