In this post, we will understand the difference between test plan and test strategy −
It is a document prepared for a software project that defines the approach, scope, and intensity required for software testing.
It can be changed.
It happens independently.
It describes the details.
It is only done by the test administrator or test manager.
It is generally utilized at the project level.
Its objective deals with how and when to test the product or system, and who would confirm it.
It is a set of instructions that explain the test design.
They also help determine how the test has to be performed.
It can’t be changed.
It is generally a part of a test plan.
It describes the general methodologies.
It is usually performed by the task manager.
It is generally used at the association level.
It consists of vital objectives of the approach that needs to be pursued, and the module that needs to be checked.
It has two techniques −
Proactive - An approach in which the test design process is initiated as early as possible in order to find and fix the defects before the build is created.
Reactive - An approach in which the testing is not started until after design and coding are completed.