Key Difference Between Test Plan and Test Strategy
•
Key Difference Between Test Plan and Test Strategy
• Test Plan is a document that describes the scope, objective and weight on software testing
task whereas Test Strategy describes how testing needs to be done.
• Test Plan is used at the project level whereas Test Strategy is used at the organization level.
• Test Plan has the primary goal of how to test, when to test and who will verify whereas Test
Strategy has the primary goal of what technique to follow and which module to check.
• Test Plan can be changed whereas Test Strategy can’t change.
• Test Plan is carried out by the test manager whereas the Test Strategy is carried out by the
project manager
What is Test Plan?
• A Test Plan is defined as a document which outlines the scope, objective,
method and weight on a software testing task
• A test plan for software project can be defined as a document that
defines the scope, objective, approach and emphasis on a software
testing effort
• A test plan for software project can be defined as a document that
defines the scope, objective, approach and emphasis on a software
testing effort
• Test plan is carried out by a testing manager or lead that describes how to
test, when to test, who will test and what to test
Test plan covers –
• Test Objectives
• In-Scope and out of scope items
• Risks
• Approach (extent of testing, automation/regression/performance test)
• Test Schedule
• Entry and Exit Criteria
• Pass/Fail criteria
• Test Deliverables (Reports, test cases, etc)
• Environmental needs
• Staffing needs
What is Test Strategy
• Test Strategy in software testing is defined as a set of guiding principles
that determines the test design & regulates how the software testing
process will be done. The objective of the Test Strategy is to provide a
systematic approach to the software testing process in order to ensure
the quality, traceability, reliability and better planning.
• Components of Test strategy includes- objectives and scope,
documentation formats, test processes, team reporting structure,
client communication strategy, etc
• Test strategy narrates about the general approaches
What are 3 testing strategies?
• The test strategy describes the test level to be performed.
• There are primarily three levels of testing:
1. unit testing
2. integration testing
3. system testing.
• In most software development organizations, the developers
are responsible for unit testing.
Test planning
Test strategy
Difference Between Test Strategy and Test Plan
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
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
