How’s Test Plan Actually Different From Test Strategy?


2 m read


Testing & QA


The Test Strategy document is usually done by the project manager. It is a document of high level and is mostly static (meaning it is not changed often). This will be a precise definition of the approach a team will be taking while testing. Testing objectives will be cleared in the Test Strategy. The document is usually driven by the business requirement specifications. The strategy document will be dedicating standards for all of the processes as well as activities of testing. This is what will be driving the Test Plan as well as many other important documents making the Test Plan but a part of a Test Strategy.

One more point adding confusion is a little fact stating many companies are including the test Strategy just inside a Test Plan for many small projects. This approach is working by the way but if we are talking a small project only, that is.

What should be included into a great Testing Strategy?

  • Objectives and scope
  • Issues related to business
  • Each team member’s role and responsibilities
  • Proper way of the communication flow and status reports
  • Test deliverability
  • Standards to be followed
  • Possible risks and ways of overcoming them
  • A proper way of defect detection as well as a way of tracking and reporting them appropriately
  • Training plan
  • Change as well as configuration management

Now to the Test Plan we go!

Test Plan takes it’s roots in SRS (Software requirement Specification) and the Product Description as the places a great Test Plan has to be derived from. It is usually written by the Test Lead/Manager in order to make specific, clear, descriptive objectives on what to test and ho will be testing those things. Often there are Test Plans for every testing phase united into one Mater test plan. A nice practice, by the way, if you are dealing with a very (very-very) big project. What are the things that must be included inside a decent Test Plan?

  • Every single Test ID to begin with
  • Introduction
  • Test Items
  • All the features that are to be tested
  • As well as the features that will not be tested
  • Techniques of testing that will be used
  • Set testing tasks
  • Suspension criteria
  • The criteria by which features pass or fail
  • Test environment
  • Deliverables
  • Testers and their need in training
  • Responsibilities of testers
  • Testing schedule

That is pretty much all everybody needs to know about both Testing Plans and Strategies.

Check out our related articles:

7 Tips on How to Write a Test Plan

7 Steps to Develop Good Test Strategy Document

7 Stages of Testing Life Cycle

Realizing the importance of providing service on agreed terms, we consider all possible risks and provide efficient solutions for all possible risks and provide efficient solutions.


We use cookies to ensure your best experience. By continuing to browse this site, you accept the use of cookies and "third-party" cookies. For more information or to refuse consent to some cookies, please see our Privacy Policy and Cookie Policy