# Test Strategy vs Test Plan

&#x20;In this post, we will see the difference between Test Strategy vs Test Plan. Before learning the difference between Test Strategy and Test Plan, let us first understand the individual concepts of Test Plan and Test Strategy in brief. In most of the interviews, you will face this question i.e., Test Strategy Vs Test Plan. Here in this post, we will show 10 differences between Test Strategy and Test Plan. Both these Test Strategy and Test Plan templates come under Test Artifacts. As a tester, these two templates are very useful in the Software Test Life Cycle (STLC).

In this tutorial, we are going to see the following

* What is a Test Strategy?
* Components of the Test Strategy document
* What is a Test Plan?
* Components of the Test Plan document
* Test Strategy vs Test Plan

#### **What is a Test Strategy?** <a href="#what-is-a-test-strategy" id="what-is-a-test-strategy"></a>

Test Strategy is a high-level document (static document) and usually developed by a project manager. It is a document which captures the approach on how we go about testing the product and achieve the goals. It is normally derived from the Business Requirement Specification (BRS). Documents like Test Plan are prepared by keeping this document as base.

**Components of the Test Strategy document**

* Scope and overview
* Test Approach
* Testing tools
* Industry standards to follow
* Test deliverables
* Testing metrics
* Requirement Traceability Matrix
* Risk and mitigation
* Reporting tool
* Test summary

Check this detailed post on [Test Strategy](https://testplace.gitbook.io/tutorials/manual-testing/manual-testing-tutorial/test-strategy)

#### **What is a Test Plan?** <a href="#what-is-a-test-plan" id="what-is-a-test-plan"></a>

Test plan document is a document which contains the plan for all the testing activities to be done to deliver a quality product. Test Plan document is derived from the Product Description, SRS, or Use Case documents for all future activities of the project. It is usually prepared by the Test Lead or Test Manager and the focus of the document is to describe what to test, what not to test, how to test when to test and who will do what test. Also, it includes the environment and tools needed, resource allocation, test technique to be followed, risks and contingencies plan. A test plan is a dynamic document and we should always keep it up-to-date. Test plan document guides us how the testing activity should go on. Success of the testing project completely depends on Test Plan.

**Components of the Test Plan document**

* Test Plan Identifier
* References
* Introduction
* Test Items
* Features To Be Tested
* Features Not To Be Tested
* Approach
* Pass/Fail Criteria
* Suspension Criteria
* Test Deliverables
* Testing Tasks
* Environmental Needs
* Responsibilities
* Staffing and Training Needs
* Schedule
* Risks and Contingencies
* Approvals

Check this detailed post on [Test Plan](https://testplace.gitbook.io/tutorials/manual-testing/manual-testing-tutorial/test-plan)

Even though testing differs between organizations. Almost all the software development organizations follow Test Strategy & Test Plan documents to achieve the goals and to follow the best practice.

#### **Test Strategy vs Test Plan** <a href="#test-strategy-vs-test-plan" id="test-strategy-vs-test-plan"></a>

| TEST STRATEGY                                                                                                                                                                                                                               | TEST PLAN                                                                                                                                                                                                                                                   |
| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Test Strategy is a high level document which captures the approach on how we go about testing the product and achieve the goals.                                                                                                            | Test plan document is a document which contains the plan for all the testing activities to be done to deliver a quality product.                                                                                                                            |
| Components of Test strategy includes Scope and overview, Test Approach, Testing tools, Industry standards to follow, Test deliverables, Testing metrics, Requirement Traceability Matrix, Risk and mitigation, Reporting tool, Test summary | Components of Test plan includes Test Plan Identifier, Features To Be Tested, Features Not To Be Tested, Approach, Pass/Fail Criteria, Suspension Criteria, Test Deliverables, Responsibilities, Staffing and Training Needs, Risks and Contingencies etc., |
| It is developed by the project manager                                                                                                                                                                                                      | It is prepared by test lead or test manager                                                                                                                                                                                                                 |
| It is derived from the Business requirement specifications (BRS)                                                                                                                                                                            | It is derived from the Product Description, SRS, or Use Case documents                                                                                                                                                                                      |
| It is a static document. Once defined, it cannot be changed                                                                                                                                                                                 | It is a dynamic document. It can be changed                                                                                                                                                                                                                 |
| It is defined at organization level and can be used for other projects of similar nature                                                                                                                                                    | It is defined at project level                                                                                                                                                                                                                              |

**Conculusion:**

Difference between Test Strategy and Test Plan has a prominent confusion among QA aspirants. Hope we have given enough explanation on this. For a detailed explanation on test strategy and test plan documents and to download sample test strategy and sample test plan document, check our tutorials on Test Strategy documentand Test Plan document.
