Test StrategyA Test Strategy document is a high level document and normally developed by project manager.
This document defines Software Testing Approach to achieve testing objectives.
The Test Strategy is normally derived from the Business Requirement Specification document.
The Test Strategy document is a static document meaning that it is not updated too often.
It sets the standards for testing processes and activities and other documents such as the
Test Plan draws its contents from those standards set in the Test Strategy Document.
Some companies include the Test Approach or Strategy inside the Test Plan,
which is fine and it is usually the case for small projects. However, for larger projects,
there is one Test Strategy document and different number of Test Plans for each phase or level of testing.
Test Strategy Vs Test Plan
Test Strategy is a high level document. In which you will be talking about complete testing project.
It will talk only on what approaches will be taken, which types of testing will be done like Performance,
Test Plan is a detailed document. You will have different test plans like Performance test plan,
Unit test plan, System/Integration test plan ......
Here you will talk in detail like how you wish to go about it, are you using any tools, Parameters that you
will be testing.... and everyting will be specific only to that particular testing (Performance,System/
Ready to start your tutorial with us? That's great! Send us an email and we will get back to you as soon as possible!