Difference between Test Strategy and Test Plan
Test Strategy Test Plan
Thought - What should be done for testing
Process or how the product will be tested?
- Overall approach for testing
- Types of testing that need to be
performed and the testing
techniques to be followed
- Finding an optimal balance
between test effort to be exerted
and coverage required for the
risks
Why - To lay emphasis on what parts or
aspects of the application should
be tested
- To communicate the testing
approach before the detailed
planning is done.
- To communicate early to the
management on any risks,
assumptions and dependencies.
When - For new initiatives or large or
complex testing projects
- Prepared at the initial phase,
when all the granular details are
not available.
- When there is impact to multiple
systems and application under
test is complex
- Mass change of application that
poses severe risks.
- How do we perform the Testing
activities?
- Implementation details of the Test
Strategy.
- Detailed planning aspects on
which would be at an operational
level.
- Logistical details of testing such
as rounds of testing, timelines,
resources, entry and exit criteria
etc…
- To explain how the test strategy
would be applied to the testing.
- To emphasis what are the
activities to be done in what
schedule and by whom.
- To ensure all tasks in testing
effort are accounted and setting
the expectations on roles and
responsibilities.
- This should be a default activity
and work product for any testing
project.
- Test plan is prepared separately
for each type of testing providing
the operational level details.
Types - Application Development Test - Manual Test Plan
Strategy
- Automation Test Plan
- Application Maintenance Test
Strategy - Performance Test Plan

- BPT Test Plan

- Maintenance Release Test Plan