Test Strategy Vs Test Plan

Test Strategy:

• A test strategy is an outline that describes the testing approach of the software development cycle. 
• Test strategy is a set of guidelines that explains test design and determines how testing needs to be done.
• The creation and documentation of a test strategy should be done in a systematic way to ensure that all objectives are fully covered and understood by all.
• It should also frequently be reviewed, challenged and updated as the organization and the product evolve over time.

Test Strategy Vs Test Plan:

Test Plan	Test Strategy
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 strategy is a set of guidelines that explains test design and determines how testing needs to be done.
Test plan include- Introduction, features to be tested, test techniques, testing tasks, features pass or fail criteria, test deliverables, responsibilities, and schedule, etc.	Test strategy includes- objectives and scope, documentation formats, test processes, team reporting structure, client communication strategy, etc.
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	A test strategy is carried out by the project manager. It says what type of technique to follow and which module to test
Test plan narrates about the specification.	Test strategy narrates about the general approaches.
It is done to identify possible inconsistencies in the final product and mitigate them through the testing process.	It is a plan of action of the testing process on a long-term basis.
It is used on a project level only.	It is used on an organizational level.
Test plan can change.	It is used by multiple projects and can be repeated a lot of times.
It is used by one project only and is very rarely repeated.	Test strategy cannot be changed.
Test planning is done to determine possible issues and dependencies in order to identify the risks.	It is a long-term plan of action. You can abstract information that is not project specific and put it into test approach

Please refer below video more details: