Monday, 29 June 2009

Purpose and content of a Test Strategy

I've often being asked by interviewers the same questions again and again and it it this: "What is the purpose of a Test Strategy document and what is the content?" and every time I was asked this question, I must have given a different answer in each case. But I thought I'd write down the definitive answer to that question so I won't have to remember it again.

A Test Strategy is either a company level document which defines the standard testing approach to be taken across all projects, or a project level document which defines the standard testing approach to be taken across all stages of testing. 


The contents of test strategy can consist of the following:
  1. Scope and Objective
  2. Budget control
  3. Testing approach
  4. Test deliverables: A list of deliverables to be produced during a software project, e.g. test plan, test cases, test data, text execution results, defect reports and test completion report.
  5. Roles and responsibilities: Identifying the type of test roles needed and each of their responsibilities, e.g. test manager, senior test analyst, tester, automated test engineer, etc.
  6. Communication and status reporting: The type of reports to be generated  and their frequency
  7. Automation tools: (if needed)
  8. Testing Measurements: How success and failures of the testing will be judged and the kind of measurements to be used to access project success
  9. Change configuration management
  10. Training plan


No comments: