Difference between Test Plan and Test Strategy

Test Strategy - Here we are going to mention what are things we are going to test with the details on methodlogoies in brief.  

Test Plan - Here we are going to talk about the type of testing we do, resource planning,Risk and Mitigation plan, Test environment, etc..... in details for a particular project. As per my knowledge using test management tools like Zephyr, the planning and scheduling process is real-time and visible to both developer and testers. It helps to make the work easy and fast.

Hi Gaurav,

Test Strategy

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

The Test Stategy document is a static document meaning that it is not updated too often. It sets the standards 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.

Some companies include the "Test Approach" or "Strategy" inside the Test Plan, which is fine and it is usually the case for small projects. However, for larger projects, there is one Test Strategy document and different number of Test Plans for each phase or level of testing.

Components of the Test Strategy document

    * Scope and Objectives
    * Business issues
    * Roles and responsibilities
    * Communication and status reporting
    * Test deliverability
    * Industry standards to follow
    * Test automation and tools
    * Testing measurements and metrices
    * Risks and mitigation
    * Defect reporting and tracking
    * Change and configuration management
    * Training plan

Test Plan

The Test Plan document on the other hand, is derived from the Product Description, Software Requirement Specification SRS, or Use Case Documents.
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.

It is not uncommon to have one Master Test Plan which is a common document for the test phases and each test phase have their own Test Plan documents.

There is much debate, as to whether the Test Plan document should also be a static document like the Test Strategy document mentioned above or should it be updated every often to reflect changes according to the direction of the project and activities.
My own personal view is that when a testing phase starts and the Test Manager is "controlling" the activities, the test plan should be updated to reflect any deviation from the original plan. After all, Planning and Control are continuous activities in the formal test process.

    * Test Plan id
    * Introduction
    * Test items
    * Features to be tested
    * Features not to be tested
    * Test techniques
    * Testing tasks
    * Suspension criteria
    * Features pass or fail criteria
    * Test environment (Entry criteria, Exit criteria)
    * Test delivarables
    * Staff and training needs
    * Responsibilities
    * Schedule





Thanks

Hi,

Test Plan covers – What needs to be tested, How testing is going to be performed? Resources needed for testing, Timelines and Risk associated.

Test Strategy – Test Strategy or Test Approach is a set of guide lines that describes test design. Test strategy says - How testing is going to be performed? What will be the test architecture?

Test Strategy can be at two levels – Company/Organization Level and Project Level. For e,g, If company is product based, then there can be a general test strategy for testing their software products. Same strategy can be implemented (with/without  some modifications) at project level whenever a new project comes.

pls refer this url for more:

http://www.softwaretestingtimes.com/2010/04/difference-between-test-plan-and-test.html

thanks

If this post is useful then mark it as "Accepted Answer"