Test Plan (Template) · Test Plan (Template) General Instructions The aim of this document is to detail what is being tested

<client_name>

<project_name>

<phase_name>

Test Plan (Template)

General Instructions

The aim of this document is to detail what is being tested in this [project / phase / level / cycle] and the approach to be employed for the <phase_name> testing stage of the <project_name>

project. It describes the scope, approach, resources and schedule of intended test activities. It also identifies the test items, features to be tested, testing tasks (and who will carry them out),

the degree of tester independence, test environment, test design techniques, entry and exit criteria to be applied and the rationale for their use.

This template includes guidelines which look like this – boxed, red text. Remove them once you understand how to use the template.

It also includes text marked in blue which should be replaced with the appropriate information

for the relevant project.

Text in grey is suggested standard text which may be replaced with content more appropriate

to your project, if preferred.

Black text relates to the structure of the document and should not normally be replaced.

This template can be used for test plans at any level, just vary accordingly the amount of detail included. If this is a lower level Test Plan it is a more detailed plan describing a particular

element of testing. It could relate, for example, to integration testing or unit testing.

All sections of this template should be included at whatever level of plan. If a section is not

relevant, enter a rationale to that effect

Document Owner

Date

State / Version

Configuration Item #

Copyright © 2017 Experimentus Ltd 01_Test_Plan_Template.docx Under License from Experimentus Ltd iTM V 6.0 Company Confidential Page 2

Table of Contents

1. DOCUMENT CONTROL ........................................................................................................................................ 4

1.1. APPROVAL RECORD ................................................................................................................................................... 4 1.2. DOCUMENT HISTORY ................................................................................................................................................. 4 1.3. REFERENCES ............................................................................................................................................................ 4 1.4. TEMPLATE HISTORY ................................................................................................................................................... 4

2. INTRODUCTION .................................................................................................................................................. 5

3. TEST ITEMS ......................................................................................................................................................... 5

4. FEATURES TO BE TESTED .................................................................................................................................... 6

5. FEATURES NOT TO BE TESTED ............................................................................................................................. 6

6. APPROACH ......................................................................................................................................................... 6

6.1. MAJOR ACTIVITIES .................................................................................................................................................... 7 6.2. TEST TECHNIQUES ..................................................................................................................................................... 7 6.3. TEST TOOLS ............................................................................................................................................................. 8 6.4. FEATURE TESTING ..................................................................................................................................................... 8 6.5. REGRESSION TESTING ................................................................................................................................................ 8

7. ITEM PASS / FAIL CRITERIA ................................................................................................................................. 9

8. ENTRY AND EXIT CRITERIA .................................................................................................................................. 9

8.1. TEST SPECIFICATION ENTRY CRITERIA ............................................................................................................................. 9 8.2. TEST SPECIFICATION EXIT CRITERIA ................................................................................................................................ 9 8.3. TEST EXECUTION ENTRY CRITERIA ............................................................................................................................... 10 8.4. TEST EXECUTION EXIT CRITERIA .................................................................................................................................. 10

9. SUSPENSION CRITERIA AND RESUMPTION REQUIREMENTS .............................................................................. 11

10. TEST DELIVERABLES ...................................................................................................................................... 11

10.1. TEST SCHEDULE ...................................................................................................................................................... 11 10.2. TEST DESIGN SPECIFICATIONS .................................................................................................................................... 12 10.3. TEST CASE SPECIFICATIONS ........................................................................................................................................ 12 10.4. TEST PROCEDURE SPECIFICATIONS (TEST SCRIPTS) .......................................................................................................... 13 10.5. RELEASE NOTE ........................................................................................................................................................ 13 10.6. TEST LOG .............................................................................................................................................................. 14 10.7. INCIDENT REPORTS .................................................................................................................................................. 14 10.8. TEST SUMMARY REPORT ........................................................................................................................................... 15

11. TESTING TASKS ............................................................................................................................................. 15

11.1. TEST PREPARATION ................................................................................................................................................. 15 11.2. TEST PLANNING ...................................................................................................................................................... 16

12. ENVIRONMENTAL NEEDS .............................................................................................................................. 16

12.1. OVERVIEW ............................................................................................................................................................ 17 12.2. INTERFACES ........................................................................................................................................................... 17 12.3. LOGICAL TEST ENVIRONMENT .................................................................................................................................... 17


12.4. PHYSICAL TEST ENVIRONMENT ................................................................................................................................... 17 12.5. TEST TOOLS ........................................................................................................................................................... 18 12.6. TEST DATA ............................................................................................................................................................. 18

13. RESPONSIBILITIES ......................................................................................................................................... 18

13.1. TEST STAGE / PHASE / LEVEL ORGANISATION ................................................................................................................ 20

14. STAFFING AND TRAINING NEEDS .................................................................................................................. 20

14.1. STAFFING NEEDS ..................................................................................................................................................... 20 14.2. TRAINING NEEDS..................................................................................................................................................... 21

15. SCHEDULE .................................................................................................................................................... 21

16. RISKS AND CONTINGENCIES .......................................................................................................................... 21

17. DEPENDENCIES, CONSTRAINTS AND ASSUMPTIONS...................................................................................... 22

17.1. DEPENDENCIES ....................................................................................................................................................... 22 17.2. CONSTRAINTS ........................................................................................................................................................ 22 17.3. ASSUMPTIONS ....................................................................................................................................................... 22

18. SIGN-OFF REQUIREMENTS ............................................................................................................................ 23

19. TESTING CONTROL AND REPORTING ............................................................................................................. 23

19.1. CONFIGURATION MANAGEMENT ................................................................................................................................ 23 19.2. CHANGE CONTROL .................................................................................................................................................. 23 19.3. ISSUE MANAGEMENT ............................................................................................................................................... 23 19.4. INCIDENT MANAGEMENT .......................................................................................................................................... 24 19.5. INCIDENT MANAGEMENT REPORTING .......................................................................................................................... 24 19.6. PROGRESS REPORTING ............................................................................................................................................. 24 19.7. TESTING METRICS ................................................................................................................................................... 24

20. APPROVALS .................................................................................................................................................. 24

Highlight and use F9 to update the table of contents


1. Document Control

1.1. Approval record

Name Role Signature/Date

Author

Approver

Reviewer

1.2. Document history

Date Version Type Reason for Change

1.3. References

No Title Document Reference (Path)

1 Organisation Test strategy

2 Account / programme test strategy

3 Project test strategy

4 Product test risk register

5 Project risk registe

1.4. Template history

Date Name Version Reason for Change

3 Mar 2017 Adrian Howes 1.0 Format change. Added template history


2. Introduction

The purpose of the introduction is to provide brief information to anyone who wants to use the test plan. Here a summary of the software items and software features to be tested is placed. The history of each item and the reason for it being included may also be documented. The

Project Master Test Plan is likely to be the highest level plan so references should be made to

the following source documents (that constitute the inputs to the test process) where they exist:

• Project authorisation • Project plan (as distinct from the project master test plan)

• Quality assurance plan • Account Test Strategy

• Configuration management plan • Relevant policies

• Relevant standards

If there are multilevel test plans then each lower-level plan will reference the next higher-level

plan.

This section need not be much longer than about half a page.

A lower level Test Plan is similar to a project master test plan, but has more detail specific to a particular level / phase of the project. The same headings are used as in the project master test

plan but in a much greater level of detail.

The Level Test Plan shows how that level / phase will be completed within the deadlines agreed

in the Project Master Test Plan. It will contain the day-to-day schedule of proposed activities and milestones and may specify a confidence pack to be completed after each new release.

Test Plans (all levels) contains the day-to-day schedule to be completed but not the specific

day-to-day testing tasks to be completed, this will be specified in the execution schedule.

3. Test items

This is a high level list of the product components that you are testing. Note that this is a list of inputs to your testing.

Here the individual test items should be identified, to include their version or revision number. If

there are any characteristics of their means of transmission that require particular hardware requirements then this should also be documented, as should any need for transformations (if,

for example, software must be transferred from one medium to another using FTP).

References should be made to:

• Requirements specifications • Design specifications

• User guides


• Operations guides • Installation guides

• Incident reports relating to the test items

(if they exist).

Items that are to be specifically not tested may also be identified.

4. Features to be tested

Summarise the release’s functionality in this section, and make clear which features are to be tested in this level / phase. Include a discussion of, for example, software modules,

configurations, enhancements, interfaces and reports.

All software features and their combinations that are to be tested should be listed. A reference

should be made linking each feature (and combination of features) to the associated test design specification.

A software feature is a distinguishing characteristic of a software item (for example,

performance, portability, or functionality). You may wish to consider a feature to be “something that can be sold to a customer”. For example, if an application runs slower than the customer

would like, increasing the speed of its most used functions can be held up as a feature. So in

this case the feature to be tested would be the performance of the most used functions.

Where functionality depends on interfaces, explain the associated systems.

If relevant, detail the technical scope. Examples include nature of test environment and

operations architecture components.

5. Features not to be tested

Explicitly state the features, functional or technical detail not included in the test stage or not being tested. The reasons behind these decisions are also documented. For certain test levels / phases this may extend to geographic locations omitted from testing (for example, certain sites)

Examples include:

• Features that are being deferred to a later incremental release • Combinations of settings or equipment configurations that cannot be tested by the date

needed to get the product to market

6. Approach

Documents

Test Plan (Template) · Test Plan (Template) General Instructions The aim of this document is to detail what is being tested