Test Strategy and Test Plan

Test Strategy

test-strategy-vs-test-plan

test-strategy-vs-test-plan

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
  • 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 deliverables
  • Staff and training needs
  • Responsibilities
  • Schedule

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

Next: Agile Test Plan – Do We Really Need One?

Related Articles

50 Comments

  1. shubhangee July 13, 2011
  2. Rahul Upadhyay July 14, 2011
  3. RaHul Tiwari July 18, 2011
  4. Joseph August 2, 2011
  5. Ramesh Reddy August 8, 2011
  6. Leo September 6, 2011
  7. arun October 11, 2011
  8. vipin October 17, 2011
  9. venkat November 27, 2011
  10. Porush January 27, 2012
  11. sampsos February 6, 2012
    • ramnoy January 23, 2015
  12. nagaswathi March 2, 2012
  13. Raghavendra N.K. March 11, 2012
  14. siddu March 28, 2012
  15. lokesh March 28, 2012
  16. thenmozhi April 3, 2012
  17. Prateek April 12, 2012
  18. Ravi` July 30, 2012
  19. syed September 13, 2012
  20. saketha October 5, 2012
  21. Sam October 5, 2012
  22. data center colocation October 9, 2012
  23. shaik nagulmeera January 2, 2013
  24. Ravi Suvvari January 10, 2013
  25. Nisha February 21, 2013
  26. Shri March 12, 2013
  27. Max June 10, 2013
  28. Anju July 3, 2013
  29. Sultana July 27, 2013
  30. Pradeep August 5, 2013
  31. hussain August 5, 2013
  32. komal October 7, 2013
  33. SHussain January 3, 2014
  34. Yagna February 12, 2014
  35. pravash February 15, 2014
  36. Sherine March 25, 2014
  37. Prasad April 26, 2014
  38. Ganesh May 5, 2014
  39. Santosh Sheelvant June 5, 2014
  40. raj November 4, 2014
  41. Lakshmi November 13, 2014
  42. sanjukta January 21, 2015
  43. Mohammad Sadique February 20, 2015
  44. Gayatri Manjani March 2, 2015
  45. Tajammul March 4, 2015
  46. Kavitha MK April 2, 2015
  47. Inder April 15, 2015
  48. Ayesha May 16, 2015
  49. divya May 27, 2015

Leave a Reply

Your email address will not be published. Required fields are marked *