Software Testing Basics

Difference between Test Strategy & Test Plan

It is very common opinion that Test Strategy & Test Plan are same. However it is very important to understand that these are separate documents and are important in their own aspect. Lets understand what is the difference between these two documents.

Test Strategy

A Test Strategy document is a high level document and generally prepared by project manager. This document defines Software Testing Approach to achieve testing objectives. The Test Strategy is normally derived from the Business Requirement Specification document.

The Test Strategy document is a static document meaning which does not need constant updating. This documents sets the principles for testing processes and activities and other documents such as the Test Plan draws its contents from those standards set in the Test Strategy Document.

For small projects, sometimes the Test Strategy is included in the Test Plan, however this approach is not good for larger projects, for which there should always be a different Test Strategy Document and a separate Test Plan.

Components of the Test Strategy document

·         Scope and Objectives

·         Business issues

·         Roles and responsibilities

·         Communication and status reporting

·         Test deliver-ability

·         Industry standards to follow

·         Test automation and tools

·         Testing measurements and metrics

·         Risks and mitigation

·         Defect reporting and tracking

·         Change and configuration management

·         Training plan

Test Plan

The Test Plan document, is derived from various project documents such as Software Requirement Specification (SRS), Use Case Documents, etc.

The Test Plan document is usually prepared by the Test Lead or Test Manager and the focus of the document is to describe what to test, how to test, when to test and who will do what test.

·         Introduction

·         Test items

·         Features to be tested

·         Features not to be tested

·         Test techniques

·         Testing tasks

·         Exit criteria

·         Pass or fail criteria

·         Test environment

·         Test deliverable

·         Responsibilities

·         Time Plan