<Client / Project Name>

Test Strategy
v1.0

Document: Test Strategy Page 1 of 9

 Document History

Document Location
This is a snapshot of an on-line document. Paper copies are valid only on the day they are
printed. Refer to the author if you are in any doubt about the currency of this document.

Document Name Document Location

Agile Test Strategy Project place

Revision History
Revision Number Revision Date Summary of Changes Changes marked
0.1 19/01/2016 Draft Version

Approvals
Name Title Approval Date Approver’s Signature

Distribution
Date Modified By Modification
15 October 2016 Developer Name Initial Document
Creation

Document: Test Strategy Page 2 of 9

 TABLE OF CONTENTS
APPROVAL FORM/SIGN-OFF.................................................................................4

1 INTRODUCTION..............................................................................................4

1.1 PURPOSE.................................................................................................................. 4
1.2 PROJECT REFERENCES.............................................................................................. 4
1.3 TESTING OBJECTIVE.................................................................................................. 4
1.4 TEST SCOPE............................................................................................................. 5
1.5 TESTLEVELS.............................................................................................................. 5
1.6 ASSUMPTIONS FOR TESTING......................................................................................6
2 TEST APPROACH / STRATEGY.....................................................................7

2.1 AGILE TESTING FRAMEWORK.....................................................................................8

2.2 AGILE TESTING WORKFLOW.......................................................................................9
3 TESTING DELIVERABLES..............................................................................9

4 TEST Plan SCHEDULE..................................................................................9

5 TEST ENVIRONMENT....................................................................................9

5.1 TEST ENVIRONMENT REQUIREMENTS..............................................................9

6 RISK IDENTIFICATION & MITIGATION..........................................................9

Document: Test Strategy Page 3 of 9

 APPROVAL FORM/SIGN-OFF

Prepared By: Role:

Test Lead

Recommended Sign-off:

Name: Role: Sign-off? Date:

Project Manager
Program Manager
Lead Test Architect

1 INTRODUCTION
This Strategy document defines the objectives, context and approach used to perform the testing
in an Agile environment; Also assesses the quality of developed software.
1.1 Purpose
This Strategy document serves as a high level plan that specifies the overall approach to
perform Testing in an Agile environment.

It documents Agile Testing framework, approach and standards that will apply to Test cases,
Functions and Object Repository’s. All test cases will be built using an Automated Function
Based Testing Methodology and by identifying tasks required to build an Agile testing
solution.

1.2 Project References

This document is based on and refers to the following documents:

Name of Document / Location of Process Document / Asset

Asset
India<CLIENT>DOU

1.3 Testing Objective

This section aligns the overall Test implementation plan for the <Client> applications
developed. It describes the tangible goals of testing. Test objectives can be at varying levels
of detail. At the Test strategy level, the test objectives are driven by the solution objectives
and describe the overall objectives for testing. These include high level objectives that
address the business functions, the technical requirements and those that reduce the risks
and costs of failure.
(This can be modified depending upon the actual scope).

Document: Test Strategy Page 4 of 9

 1.4 Test Scope

Need to mention what are the applications / Features in scope / Out of Scope. Anything
except those requirements (FR) that have been formally agreed upon by both <Client> and
IBM and documented accordingly in DoU is considered out of scope.

More details would be covered in a Test plan for the respective Release / Features.

Applications / Features Description In Scope Out of Comments

Features Scope

1.5 TestLevels

Below diagram shows the Agile Testing Quadrants and various Test levels. The Test Levels
applicable for specific engagement to be chosen and provided in this section–-

Document: Test Strategy Page 5 of 9

 Test Phases Definition In Scope Out Scope Comments

App Testing Application testing deals with tests

for the entire application which is
driven by the requirements.
Service Testing Establishing that the connectivity with
the Services
Integration Performing Integration testing
Testing connecting the Application with the
services.
Non- Functional Testing the attributes of a component
or system that do not relate to
functionality, e.g. reliability, efficiency,
usability, maintainability, and
portability.
Production Allows the user to perform a final
Assurance(UAT) check and confirm functionality
volume, accuracy, interfaces, etc.
based on business requirements, using
production data.

1.6 Assumptions for Testing

Any underlying assumptions for the strategy is clearly stated in this section.

2 TEST APPROACH / STRATEGY

The testing strategy should introduce the client to the concept of using facilitated joint planning
sessions of all stake holder representatives to define the test strategy.  This should be treated as
Document: Test Strategy Page 6 of 9
 part of the Organization Change Management activities, as many organizations know the
importance of good and effective testing methods and practices. 

Below is the IBM Recommended Operating Model for an Agile testing project – From Test Design
to Automated Test Cases. This approach delivers lowest test case volume with highest coverage.
It provides a tool suite that operationalizes and automates testing in the DevOps process.

The diagram below shows IBM’s Integration Architecture that drives optimization and
automation across the testing lifecycle.

Note - This is the general IBM proposed Test Model and Integration architecture. The Model and
architecture that would be implemented for a specific client engagement to be replaced after
walkthrough.

2.1 Agile Testing Framework

The diagram will serve as a guide to the testing team on the list of activities and tasks that need
to be performed from a Testing perspective. It shows the tests and tools supporting an E2E
DevOps Framework that should be used for interaction across the client organization from a
continuous integration, continuous testing and continuous deployment perspective. However, it

Document: Test Strategy Page 7 of 9

 should be noted that the principles of DevOps as applied to the development teams and various
departments or applications can also be applied to the Testing department as well. The process
starts with the functional tester(s) analyzing the user stories to determine if they are testable. It
also explains what goes into the Continuous Integration (CI) / Continuous Deployment (CD)
orchestration bucket from a testing perspective. In the sense that test automation scripts, when
first checked into the BitBucket code repository, should be tied to a Bamboo task so that it can be
triggered as part of a smoke build test. Changes to test automation script code may also trigger
Bamboo tasks tied to certain smoke test runs as part of a check in process. Such as running of
the affected test(s) to ensure that the test(s) themselves are not broken. The workflow below
describes and highlights the Agile testing lifecycle in a DevOps environment.

This is the general IBM proposed Agile Testing framework. The framework that would be
implemented for a specific client engagement to be replaced after walkthrough.

2.2 Agile Testing Workflow

The workflow to describe the Sprint Execution process end-to-end.

Document: Test Strategy Page 8 of 9

 3 TESTING DELIVERABLES
This section lists the Testing deliverables like Test Plan Document / Test Cases / Test Result
Report / Defect Report.

4 TEST Plan SCHEDULE

Schedule timeline for every Test Plan creation per release to be followed according to the chart
given below:

Test Plan Creation Test Plan Creation

Task Description - Start Date - End Date
Due Dilligence , Discovery and Design    
Release Planning
Test Plan Creation – Release 1    
Test Plan Creation - Release 2    
……
Test Plan Creation - Release n

5 TEST ENVIRONMENT
5.1 TEST ENVIRONMENT REQUIREMENTS

Test Environment requirements to be mentioned. Also mention who would be responsible for
the Test Environment setup. The tentative dates for the test Environments for each test type
should be provided.

6 RISK IDENTIFICATION & MITIGATION

List the project related risks and mitigation plans related to Handoffs, Resources, Devices,
Defects, Environment Downtimes, Test Data.

Document: Test Strategy Page 9 of 9