An organization that develops and maintains an e-commerce platform defines a test strategy stating that all projects will perform component, integration, system, and acceptance testing; that regression testing is automated and runs on every build; and that risk-based testing guides where effort is invested. Each project then writes a test plan that applies this strategy to its own scope, schedule, and resources.
What is the difference between a test strategy and a test plan? A test strategy is a high-level description of the test levels to be performed and the testing within them, for an organization or programme. A test plan applies that strategy to a specific project with concrete scope, approach, resources, and schedule.
Who owns the test strategy? Typically the organization’s test management or QA function. Because it spans multiple projects, it is agreed at the organizational or programme level.
Can a project deviate from the strategy? Yes, with justification. The test plan records the rationale for any deviation, such as skipping a level for a small maintenance release.
Is a test strategy a document or an approach? Both. It is a documented high-level description that is implemented through project-level test plans.
