SDLC - Establish Test Strategy

Skip repetitive navigation links.

Establish Test Strategy

The Test Strategy defines the strategic plan for how the test effort will be conducted against one or more aspects of the target system. The main purpose of the Test Strategy is to:

Convey the strategy to external stakeholders to gain their agreement to the approach.

Convey the strategy to the internal members of the test team to enable a coordinated team effort.

A Test Strategy needs to be able to convince management and other stakeholders that the approach is sound and achievable, and it also needs to be appropriate both in terms of the software product to be tested and the skills of the test team. The Test Strategy should include:

An explanation of the general approach that will be used. For example, explain how the primary approach should be based on verifying the software against requirements or design specifications.

The specific types, techniques, styles of testing that will be employed as part of the strategy, and for each:

An indication of the scope and applicability of the technique.

An outline of how the technique will be employed.

An outline of what tools will be required to support the technique.

The criteria for measuring the success and ongoing value of employing the technique.

An indication of the weaknesses or limitations of the technique and where any other techniques will cover this.

Note: The Test Strategy can be readdressed continually as the project life cycle evolves.

To get started developing the Test Strategy, refer to the Test Strategy template .

Project Initiation & Portfolio Management

Requirements & Analysis

High Level Design

Allocate Functionality

Model Data

Design System Interface

Establish Test Strategy

Develop Proof-of-Concept

QC Artifact Submission

Detailed Design

Construction & Assembly

Independent Verification

Release & Maintenance

Retirement

Last Modified: 12/12/08 9:52:00 AM