Difference b/w test plan & test strategy?

Hello Guys,

Could you please clarify me what is the major diff b/w test plan & test strategy ??

Who will prepare test plan & test strategy document?


Hello @subbu!

In practice, I use the test strategy to describe what the team will test for in a product. I include an overview of the product and information objectives.
If I write a test plan, I use it to describe how I will implement the test strategy. I include testing methods, use of automation for testing or data generation, how results are reported, and possibly estimates.

As a Test Lead, I have prepared both documents. The documents are one or two pages because I’m rarely convinced that anyone will read them. If I get questions, I consider that a victory and an opportunity to engage the project team on a more personal basis.




I made the same question in my team a few months ago and the responses were a little different from everyone, but we decided some things in common.

Overall, the documentation is the test manager’s task. Both documents can be brief, or large enough to bore anyone (and no one will read it anyway…), even some companies don’t create any documentation.

For us the test plan was more like an specification of how all the testing was going to be done in the project (schedule, planning, design, execution, etc…including the strategy), and the test strategy was more about the testing policies, point of view, decisions about techniques and design of the testing more for the specific product than general like a plan.

Don’t know if it helped.


1 Like

Strategy = path, more abstract, a whole vision, road map explaining what are our strategic priorities to attain the vision and mission of testing.
Plan = allocates in detail resources that are necessary to accomplish the strategy, what is to be achieved, how and when to be achieved, how to be monitored including the performance indicators. It defines a path to be followed in order to achieve stipulated goals.


Test plan:A test plan derived from software requirement specification describing in detail the scope of testing and the different activities perform in the testing. A test plan is specific to particular project.

Test strategy:A test strategy is the high level document describing the way testing is carried out. A strategy normally for a complete organization. Although it can be specified for a particular project as well

Hello there,
Here is a good article discussing a difference between test strategy and STP.
Also we use this template to write the test strategy.

As for your question of who prepares the document - we have a PM who fills it during the meeting with the relevant customer(s)

1 Like

Test Strategy and Test Plan both are the major part of Software Test Life Cycle (STLC) used by most of the software testing services provider and these may often be confused as same per the name suggests.

Test Strategy is the high level document, static in nature and mostly developed by Project Manager. Its the document that explains that how are we going to go with testing using an approach to achieve the goals on time. This Test Strategy is derived from the Business Requirement Specifications those are being provided by the customer in beginning of any testing project. Test Plan document is further prepared with keeping this document as the base document.

Following are the main components of Test Strategy document:

  • Scope and overview of the project
  • Testing Approach to be followed
  • Testing tools to be used
  • Industry standards to be followed while testing
  • Test deliverable to be managed on time
  • Testing metrics to be followed
  • Requirement Traceability Matrix maintained
  • Risk and mitigation included
  • Reporting tools to be used
  • Test summary

Test Plan document is the guide of Testing activities to be performed while testing the product to ensure the quality of testing deliverable. Test Plan document is prepared using the information from Product Description, SRS and Use Case documents provided defining all future activities of the project. Test Plan document generally is created by Test Lead or Test Manager and the focus of this document remains on describing what to test, what not to test, how to test when to test and the responsibilities for individuals describing there part in this testing process. It also includes the environment to perform testing on, tools needed to perform testing, resource allocation according to the testing requirement, testing techniques to be followed, risks involved and contingencies plan. Test plan is a dynamic document and it should always be kept up to date.

Following are the main components of the Test Plan document:

  • Test Plan Identifier
  • References for testing
  • Introduction to product
  • Test Items to be included while testing
  • Features To Be Tested with determining severity
  • Features Not To Be included while testing
  • Approach followed to test
  • Pass/Fail Criteria determining test state
  • Suspension Criteria
  • Test Deliverable to be provided
  • Testing Tasks to be performed
  • Environmental Needs for testing
  • Responsibilities for the resources involved
  • Staffing and Training Needs for resources
  • Schedule
  • Risks and Contingencies involved
  • Approvals required

These are the main points describing the differences between Test Plan and Test Strategy. Hope this helps!