Test Strategy and Test Plan

What is the difference between test strategy and test plan?
Who prepares test strategy and test plan?
Is it necessary to have test strategy and test plan? Can we use any one? Elaborate

Questions by sweety   answers by sweety

Showing Answers 1 - 7 of 7 Answers


  • Jun 19th, 2015

Test plan will be prepared by any of the team member and in that test plan test strategy is also included.

Test plan gives the overall preview of the project and test strategy gives the approach of the process. It is necessary to prepare test plan as well as test strategy.

Lal krishna kumar

  • Jun 25th, 2015

Oop itemphasizes on data rathar than procedure.
Pop it emphasizes on doing things or algorithms.

  Was this answer useful?  Yes


  • Aug 6th, 2015

Test Plan we define scope of project, Risk, enter criteria, exit criteria these things should be define Features to be tested Features not to be tested Test techniques.

Test Strategy we can define scope of project which resources are working on that project, what is his/her responsibility, which automation tool we use in project, Defect reporting and tracking
Change and configuration management, Staff and training needs, Responsibilities, Schedule, Training plan....


  • Aug 7th, 2015

Difference in detail:
A Test Strategy document is a high level document and normally developed 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 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 deliverables
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

Here is an example of an Agile Test Strategy Document Template
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.

Components of the Test Plan document

Test Plan id
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 deliverables
Staff and training needs

This is a standard approach to prepare test plan and test strategy documents, but things can vary company-to-company.

Test plan is a term and a deliverable. Test plan is a document that lists all the activities in a QA project, schedules them, defines the scope of the project, roles & responsibilities, risks, entry & exit criteria, test objective and anything else that you can think of. Test plan is referred to the planning of the testing plan.Assigning roles and responsibilities to the testing team

  Was this answer useful?  Yes

Give your answer:

If you think the above answer is not correct, Please select a reason and add your answer below.


Related Answered Questions


Related Open Questions