Beruflich Dokumente
Kultur Dokumente
The template contains six sections that should be updated with information applicable to the software being tested.
Complete the relevant sections:
1. Test Overview
2. Test Schedule
3. Test Resources
4. Test Environment
5. Defect Tracking
6. Test Metrics
1
Application Test Strategy Template
ITA Premium: Implement & Integrate
Cover Sheet
Notes on Usage: In order to use this template effectively, overwrite text that is in italics and colored grey with the
enterprises own information.
2
Application Test Strategy Template
ITA Premium: Implement & Integrate
1. Purpose
The purpose of the test strategy document is to inform project management and project sponsors of the approach
that will be taken with testing. This document strives to ensure that the budget, start up time, facilities, and
resources are anticipated and approved prior to the start of the testing phase.
Describe additional reasons for having a test strategy this section. The purpose should include project statements
or links to other project documents like the charter. The testing effort should be described in the context of the
purpose of the overall project with links to external information that not all people may be aware of.
2. Test Overview
2.1 Test Objectives
The following are the objectives of the test strategy document.
The test objectives should include information such as a summary of the products being tested, testing aims and
goals, high-level schedule, etc.
Example: The overall test effort will commence on DD/MM/YYYY and will be executed for a period of X
months. The test effort is scheduled for completion on DD/MM/YYYY.
Example: All high priority requirements must pass through 2 rounds of successful application testing prior
to sign-off.
Refer to ITA Premium research note, Set Your Sights on the Six Software Testing Targets to understand the six
types of testing recommended to achieve a high quality end product: Unit Testing, Functional Testing, System
Testing, Regression Testing, System Integration Testing, and Acceptance Testing.
Example: The testing effort will involve six phases of testing to be executed in the following order: unit
testing, functional testing, system testing, regression testing, system integration testing, and acceptance
testing.
Example: The unit test phase will commence on DD/MM/YYYY and will run for 4 weeks throughout the
development effort.
3
Application Test Strategy Template
ITA Premium: Implement & Integrate
4
Application Test Strategy Template
ITA Premium: Implement & Integrate
3. Test Schedule
The test schedule outlines the dates during which each phase of testing is planned to take place. In addition, it
includes key milestones for each testing effort and specifies the milestone date.
In this section, discuss points regarding how testing will be scheduled taking into consideration the way the project
is being run.
For example, the project may involve multiple releases and the overall release testing schedule could be
included in this section.
Alternately, the project may be using an iterative approach and it may be necessary to state that testing for
one iteration overlaps the requirements/design piece of the next iteration.
Table 1 describes the known start and end dates of the various phases of testing. It also includes key milestones
and their corresponding dates.
Test Phase Start Date End Date Duration Key Milestones Milestone Date
Example: DD/MM/YYYY DD/MM/YYYY 70 work days Complete Draft DD/MM/YYYY
Overall Test Test Plan
Effort Achieve Test DD/MM/YYYY
Plan Sign-off
from Project
Management
Example: Unit DD/MM/YYYY DD/MM/YYYY 15 work days Complete Unit DD/MM/YYYY
Testing Test Plan
Unit Test major DD/MM/YYYY
components
A,B, and C
5
Application Test Strategy Template
ITA Premium: Implement & Integrate
4. Test Resources
The following resources will be completely or partially dedicated to the testing effort. The roles each will play in the
testing phase are as follows:
List the people that will be executing testing and the role(s) each will play. Specify which testing phase the resource
will take part in.
Resource 3 Installation, On-line user documentation System Test, System Integration Test,
Regression Test
6
Application Test Strategy Template
ITA Premium: Implement & Integrate
5. Test Environment
The following criteria must be met to fulfill the test environment requirements.
7
Application Test Strategy Template
ITA Premium: Implement & Integrate
6. Defect Tracking
The following process defines how to raise, track, and resolve defects found throughout testing.
Describe how defects will be raised, tracked, communicated, and resolved. Where possible, use a process flow
diagram to describe how the various teams involved in testing will interact to reach issue resolution.
A defect priority level can be used along with severity to help determine the urgency in fixing the defect. When
assigning a severity or priority to a defect, the following scale can be used to help assigning rankings:
Severity Scale
o High: A major issue where a large piece of functionality or major system component is completely
broken. There is no workaround and testing must halt.
o Medium: A significant issue where a large piece of functionality or major system component is not
working properly. There is a workaround, however, and testing can proceed.
o Low: A minor issue that imposes some loss of functionality, but for which there is an acceptable
and easily reproducible workaround. Testing can proceed without interruption.
Priority Scale
o High: This has a major impact on the customer. This must be fixed immediately.
o Medium: This has a major impact on the customer. The problem should be fixed before release of
the current version in development, or a patch must be issued if possible.
o Low: This has a minor impact on the customer. The flaw should be fixed if there is time, but it can
be deferred until the next release.
8
Application Test Strategy Template
ITA Premium: Implement & Integrate
7. Test Metrics
Test metrics provide a vehicle to communicate testing progress to the project team. The following information will
be collected from test results to develop testing metrics.
In the table, list the information that should be recorded for metric calculations.
Examples:
Functional Metrics: Number of requirements verified (may be broken down by testing phase, component,
testing resource or all of the above)
Code Metrics: Percent of code executed (may be broken down by test and/or component)
Problem Metrics: Problems found per day, problems found per component
Schedule Metrics: Percent of tests completed
Estimated days to completion
Time to complete testing by component
9
Application Test Strategy Template
ITA Premium: Implement & Integrate
The Test Strategy Sign-off section allows the person(s) acting as the Test Manager, Project Manager and Business
Sponsor to indicate they have reviewed the strategy and approve the content. The person(s) who are required to
review the document and sign-off should be established during the initial project planning phase.
_____________________________________________________
Info-Tech Research Group tools and template documents are provided for the free and unrestricted use of
subscribers to Info-Tech Research Group services. Use this document either in whole or in part as a basis and
guide for document creation. To customize this document with corporate marks and titles, simply replace the Info-
Tech Information in the Header and Footer fields of this document.
10