Professional Documents
Culture Documents
guru99.com/test-plan-v-s-test-strategy.html
Test Plan V/s Test Strategy is a prominent confusion among multiple levels of QA Aspirants
A test plan for software project can be defined Test strategy is a set of guidelines that
as a document that defines the scope, explains test design and determines how
objective, approach and emphasis on a testing needs to be done
software testing effort
Components of Test plan include- Test plan id, Components of Test strategy includes-
features to be tested, test techniques, testing objectives and scope, documentation
tasks, features pass or fail criteria, test formats, test processes, team reporting
deliverables, responsibilities, and schedule, structure, client communication strategy,
etc. etc.
Test plan is carried out by a testing manager A test strategy is carried out by the project
or lead that describes how to test, when to manager. It says what type of technique
test, who will test and what to test to follow and which module to test
Test plan narrates about the specification Test strategy narrates about the general
approaches
1/2
A test plan exists individually In smaller project, test strategy is often
found as a section of a test plan
2/2