Ministry/Agency Name Project Name Project #: Testing Strategy

Prepared by: Prepared for: Date Submitted: Project Sponsor: Client Acceptor: Project Manager:

Author's Name [Company Name] [Date] Project Sponsor's Name [if different than Sponsor] [Project Managers Name]

Document Number: 6450-20/Project Number /Testing Strategy Security Classification: Low Version: 0.1 Last Updated: Creation Date: January 23, 2012 [Date]

About this template: This template uses built in styles to assist the author in preparing the layout of the document. For assistance with styles, please contact the Project Support Office:

Testing Strategy

Project Name

Table of Contents
Table of Contents.............................................................................................................. 2 1. Introduction..................................................................................................................... 3
1.1. Audience..........................................................................................................................3

2. Testing Strategy Overview............................................................................................. 4

3. Background..................................................................................................................... 5 4. Scope............................................................................................................................... 6
4.1. Testing Tasks...................................................................................................................6 4.2. Test Types by Task..........................................................................................................6 4.3. Converted Data Sources..................................................................................................7 4.4. System Interfaces.............................................................................................................7 4.5. Testing Environments.......................................................................................................8 4.6. Testing Tools....................................................................................................................8

5. Constraints...................................................................................................................... 9 6. Key Inputs..................................................................................................................... 10 7. Task Overview............................................................................................................... 11 8. Key Deliverables........................................................................................................... 12 9. Acceptance Criteria...................................................................................................... 13 10. Problem Management................................................................................................14 11. Critical Success Factors............................................................................................ 15 12. Risk and Contingency Plans......................................................................................16 13. Metrics......................................................................................................................... 17 Revision Log.................................................................................................................... 18 Appendices...................................................................................................................... 19 Approval........................................................................................................................... 20

Last revised: 2012-01-23 /var/www/apps/conversion/tmp/scratch_4/179004790.doc

Page 2 of 20 Security Classification: Low

Testing Strategy

Project Name

1.

Introduction

This document provides the Testing Strategy for the <Application Name> system. It includes the following components:

1.1.

Testing Strategy Overview Background Scope Constraints Key Inputs Task Overview Key Deliverables Acceptance Criteria Problem Management Critical Success Factors Risk and Contingency Plans Metrics

Audience

The audience for this document includes system development team members, <Company Long Name> project team members, and members of the Project Name steering committee.

Last revised: 2012-01-23 /var/www/apps/conversion/tmp/scratch_4/179004790.doc

Page 3 of 20 Security Classification: Low

Testing Strategy

Project Name

2.

Testing Strategy Overview

The <Application Name> Testing Strategy determines the projects approach to testing. The strategy looks at the characteristics of the system to be built, the project time line and budget, and plans the breadth and depth of the testing effort. The Testing Strategy will influence tasks related to test planning, test types, test script development, and test execution.

2.1.

Objectives

The key objectives are as follows: Determine the significance, or critical nature, of the application system to the business. Determine the types of tests required by each testing task. Identify the need for converted data from legacy systems or other sources. Determine the need for a systems integration test by identifying key system interfaces. Identify performance assurance requirements.

2.2.

Deliverable Audience

The <Application Name> Testing Strategy is intended for the following audience: <Development Contractor> and <Company Short Name> analysts and designers <Development Contractor> and <Company Short Name> testers

conversion and interface teams operations other team members that may be involved in the systems integration test

2.3.

Benefits

The Testing Strategy can provide the following benefits: faster development of testing requirements by directly using key project deliverables earlier identification of testing requirements independence of testing from development tasks and resources

well-defined tests progressive and additive test tasks

Last revised: 2012-01-23 /var/www/apps/conversion/tmp/scratch_4/179004790.doc

Page 4 of 20 Security Classification: Low

Testing Strategy

Project Name

3.

Background

Last revised: 2012-01-23 /var/www/apps/conversion/tmp/scratch_4/179004790.doc

Page 5 of 20 Security Classification: Low

Testing Strategy

Project Name

4.

Scope

To define the testing scope of <Application Name>, the following areas were examined:

testing tasks test types by task converted data sources system interfaces testing environments testing tools

4.1.

Testing Tasks

This project includes the following testing tasks: module test module integration test system test systems integration test acceptance test

4.2.

Test Types by Task

The following list identifies, by testing task, the types of testing that will be conducted: Module Test system process step validation calculation error handling database auditing security volume data help text checkpoint restart user interface report layout screen layout Module Integration Test system process script security volume data System Test initial system documentation manual data load system process sequence using scripted data
Last revised: 2012-01-23 /var/www/apps/conversion/tmp/scratch_4/179004790.doc Page 6 of 20 Security Classification: Low

Testing Strategy

Project Name

interface using scripted data converted data load converted data inspection system process sequence using converted data interface using converted data parallel legacy reconciliation job stream backup and recovery database auditing data archival security locking batch response time online response time Systems Integration Test systems integration process sequence using converted data network stress security locking batch response time online response time Acceptance Test batch response time online response time parallel running live data live environment final system documentation sign-off

4.3.

Converted Data Sources

The following table identifies legacy or other sources of converted data that will be used for testing:
Legacy System or Source Name Description of Converted Data

4.4.

System Interfaces

The following table identifies key system interfaces that will be integral to the testing of <Application Name>:
System Interface Name Type (input, output, two-way)

Last revised: 2012-01-23 /var/www/apps/conversion/tmp/scratch_4/179004790.doc

Page 7 of 20 Security Classification: Low

Testing Strategy

Project Name

System Interface Name

Type (input, output, two-way)

4.5.

Testing Environments

The following table documents the testing environment criteria for each testing task:
Testing Task Module Test Module Integration Test System Test Systems Integration Test Acceptance Test Platform Database Name

4.6.

Testing Tools

The following testing tools will be used:

Last revised: 2012-01-23 /var/www/apps/conversion/tmp/scratch_4/179004790.doc

Page 8 of 20 Security Classification: Low

Testing Strategy

Project Name

5.

Constraints

The project must operate within the following limits: Time Testing tasks will be constrained by time, affecting the following activities:

Required System Resources The <Application Name> testing effort is restricted by the availability of the following system resources:

Business The <Application Name> testing effort is restricted by the following business policies:

Technical The <Application Name> testing effort is restricted by the following technical constraints:

Last revised: 2012-01-23 /var/www/apps/conversion/tmp/scratch_4/179004790.doc

Page 9 of 20 Security Classification: Low

Testing Strategy

Project Name

6.

Key Inputs

Key inputs to <Application Name> testing are as follows:

System Process Model System Function Model System Data Model Existing System Interfaces System Interfaces Requirements Detailed System Interfaces Requirements User Interface Style Definition Recovery and Fallback Strategy Database Object Authorization Scheme Module Process Model Menu Structure Module Functional Documentation Module Technical Documentation Installation Plan System Operations Guide User Reference Manual User Guide Technical Reference Manual Runtime Online Help business analysts operations staff

Last revised: 2012-01-23 /var/www/apps/conversion/tmp/scratch_4/179004790.doc

Page 10 of 20 Security Classification: Low

Testing Strategy

Project Name

7.

Task Overview

The key testing tasks for <Application Name> are as follows:

Develop Testing Strategy Develop System Process Test Model Develop Module and Module Integration Test Plan Perform Module Test and Module Integration Test Develop System Test Plan Prepare System Test Environment Perform System Test Develop Systems Integration Test Plan Develop Systems Integration Test Sequences Perform Systems Integration Test Prepare Acceptance Test Environment Support Acceptance Test

Last revised: 2012-01-23 /var/www/apps/conversion/tmp/scratch_4/179004790.doc

Page 11 of 20 Security Classification: Low

Testing Strategy

Project Name

8.

Key Deliverables

The key testing deliverables for <Application Name> are as follows:

Testing Strategy System Process Test Model Module and Module Integration Test Plan Module and Module Integration Test Results System Test Plan System Test Environment System Test Results Systems Integration Test Plan Systems Integration Test Sequences Systems Integration Test Results Acceptance Test Environment Acceptance Test Results

Last revised: 2012-01-23 /var/www/apps/conversion/tmp/scratch_4/179004790.doc

Page 12 of 20 Security Classification: Low

Testing Strategy

Project Name

9.

Acceptance Criteria

This acceptance criteria for the testing task deliverables will be measured by the completion and sign-off of each deliverable which has been listed. Deliverables for test scripts and test results will be subject to quality reviews.

Last revised: 2012-01-23 /var/www/apps/conversion/tmp/scratch_4/179004790.doc

Page 13 of 20 Security Classification: Low

Testing Strategy

Project Name

10.

Problem Management

The assessment and prioritization of defects found during testing will be strictly controlled using the Problem Management process described in the Master Project Plan.

Last revised: 2012-01-23 /var/www/apps/conversion/tmp/scratch_4/179004790.doc

Page 14 of 20 Security Classification: Low

Testing Strategy

Project Name

11.

Critical Success Factors

In addition to the Project Name overall critical success factors, the following critical success factors are specific to the Testing process:

Testing considerations must begin in the early phases of the project.

Test script development must be based on key project deliverables. Testing must be objective and must be performed by an independent test team (other than the programmers responsible for the application software). The problem management process must be functional as soon as testing begins, and must ensure that only valid and non-duplicated defects are processed. Multiple iterations for each testing task should be planned to allow for a higher density of testing for the current test iteration and scheduled fixes for the next iteration. Planning for the systems integration test should start early, as it will involve multiple projects, systems, and organizations. The scope of the regression test should be well defined.

An automated tool should be used to perform regression testing. Locking, response time, and stress testing should use process-based testing scripts. Modules should be categorized by their relative importance to the business for defect prioritization and performance testing.

Last revised: 2012-01-23 /var/www/apps/conversion/tmp/scratch_4/179004790.doc

Page 15 of 20 Security Classification: Low

Testing Strategy

Project Name

12.

Risk and Contingency Plans

Identified testing risks and their associated contingency plans include the following:
ID 1 2 3 4 5 Rank Risk Statement Probability Lo/Med/Hi Impact Lo/Med/Hi Mitigation

Last revised: 2012-01-23 /var/www/apps/conversion/tmp/scratch_4/179004790.doc

Page 16 of 20 Security Classification: Low

Testing Strategy

Project Name

13.

Metrics

Key testing metrics are as follows:

number of test iterations planned for each test task relative importance of the application system to the business complexity of the application system under test

number of functional areas involved in the module and module integration test number of system processes

number of scenarios per system process number of test steps per scenario complexity of the module under test complexity of the scenario under test number of other application systems in the systems integration test required online response time for critical modules batch nightly window response time number of end users required for the stress test

Last revised: 2012-01-23 /var/www/apps/conversion/tmp/scratch_4/179004790.doc

Page 17 of 20 Security Classification: Low

Testing Strategy

Project Name

Revision Log
Date [yyyy-mm-dd] Version 0.1 Change Reference Author Reviewed by

Last revised: 2012-01-23 /var/www/apps/conversion/tmp/scratch_4/179004790.doc

Page 18 of 20 Security Classification: Low

Testing Strategy

Project Name

Appendices
Enter content here.

Last revised: 2012-01-23 /var/www/apps/conversion/tmp/scratch_4/179004790.doc

Page 19 of 20 Security Classification: Low

Testing Strategy

Project Name

Approval
This document has been approved as the official Testing Strategy for the Project Name project. Following approval of this document, changes will be governed by the projects change management process, including impact analysis, appropriate reviews and approvals, under the general control of the Master Project Plan and according to Project Support Office policy.

Prepared by Author's Name [Title] [Organization]

Signature

Date

Accepted by [Client Acceptors Name] [Title] [Organization]

Signature

Date

Approved by [Client Approvers Name] [Title] [Organization] [Client Approvers Name] [Title] [Organization] [Project Managers Name] [Title] [Organization] [IMG Approvers Name] [Title] [Organization]

Signature

Date

Last revised: 2012-01-23 /var/www/apps/conversion/tmp/scratch_4/179004790.doc

Page 20 of 20 Security Classification: Low