<Project> Test Strategy

[Insert Project Name]

Test Strategy

Executive Sponsor – [Insert Name]
Business Owner - [Insert Name]
Project Manager – [Insert Name]
Original Plan Date: [Insert Date, Spelled Out]
Revision Date: [Insert Date, Spelled Out]

Revision History

Revision Number / Date / Comment
1.0 / August 14, 2007 / Original DoIT PMO Document

Table of Contents

Revision History 2

1 Introduction 4

2 Test Objectives 4

3 Identify Test Types 4

4 Scope of Testing 5

5 Test Preparation and Execution Process 6

5.1 Test Preparation 6

5.2 Test Execution 6

6 Test Data Management 7

1 Introduction

The Test Strategy documents the overall strategy for testing the processes and applications to be delivered by the project. The objectives of this document are:

·  Communicate the scope and phases of testing

·  Communicate the components that will be tested

·  Communicate the dependencies between testing phases and other projects

·  Communicate how the testing processes will be completed and managed

2 Test Objectives

[Describe the objectives of testing. Testing should ensure that the future business processes, together with the enabling technology, provide the expected business benefits. Testing objectives could include:

·  Verify products against their requirements (i.e. was the product built right?)

·  Validate that the product performs as expected (i.e. was the right product built?)

·  Ensure system components and business processes work end-to-end

·  Build a test model that can be used on an ongoing basis

·  Identify and resolve issues and risks.]

3 Identify Test Types

[Describe the types of tests to be conducted to verify that requirements have been met and to validate that the system performs satisfactorily. Consider the types of tests in the table below.]

Type of test / Definition
Unit Testing / Testing conducted to verify the implementation of the design for one software element (e.g., unit, module)
Integration Testing / An orderly progression of testing in which software elements, hardware elements, or both are combined and tested until the entire system has been integrated
System Testing / The process of testing an integrated hardware and software system to verify that the system meets its specified requirements
Acceptance Testing / Formal testing conducted to determine whether or not a system satisfies its acceptance criteria and to enable the customer to determine whether or not to accept the system
Performance Testing / Performed to confirm that the system meets performance goals such as turnaround times, maximum delays, peak performance, etc.
Volume Testing / Tests the system to verify that the system can handle an expected volume profile
Stress Testing / Tests the entire system to find the limits of performance
Configuration Testing / Tests the product over all the possible configurations on which it is supposed to run
Operational Readiness Testing / Tests the system to find defects that will prevent installation and deployment by the users
Data Conversion and Load Testing / Performed to verify the correctness of automated or manual conversions and/or loads of data in preparation for implementing the new system

4 Scope of Testing

Describe the scope of testing. Consider the following when defining scope:

·  Test both business processes and the technical solution

·  Specify regions and sub-regions included in testing

·  Identify interfaces with other projects

·  Identify interfaces with external entities such as dealers, suppliers, and joint ventures

5 Test Preparation and Execution Process

5.1 Test Preparation

Describe the steps for preparing for testing. The purpose of Test Preparation is to verify that requirements are understood and prepare for Test Execution. Steps for Test Preparation may include:

·  Identify test cases

·  Identify test cycles

·  Identify test data

·  Develop expected results

·  Develop test schedule (may be done as part of Test Plan)

·  Obtain signoff

5.2 Test Execution

Describe the steps for executing tests. The purpose of Test Execution is to execute the test cycles and test cases created during the Test Preparation activity, compare actual results to expected results, and resolve any discrepancies. Steps for Test Execution may include:

·  Verify entry criteria

·  Conduct tests

·  Compare actual results to expected results

·  Investigate and resolve discrepancies

·  Conduct regression test

·  Verify exit criteria

·  Obtain signoff

6 Test Data Management

Describe the approach for identifying and managing test data. Consider the following guidelines:

·  System and user acceptance tests – a subset of production data could be used to initialize the test environment. Because the focus of these tests is to simulate the production environment and validate business transactions, data integrity is extremely critical.

·  Performance/volume/stress test – full size production files should be used to test the performance and volume aspects of the test. Additional ‘dummy’ data will be created to stress the system. Data integrity is not critical, as the test focuses on performance rather than the ability to conduct business transactions.

·  Operational readiness test – a copy of system/user acceptance test data could be used for the operational readiness test. Since the focus of the test is on operational procedures, a low number of transactions will be required and data integrity is not critical.

Page 2 of 7