Sum of the following questions:
1. What to do? -> results in scope and deliverables
2. When to perform? -> results in schedule
3. Who will be doing? -> results in resource allocation
4. What can be the obstacles in doing things? -> results in Risk
planning and mitigation.
5. How to perform and deliver Quality Quickly? -> results in Test
So, Test Strategy is a part of Test plan.
What should be in Test Strategy?
Test Strategy is used as a communication tool to build the confidence
to the stakholders that QA understood the intent of the feature/system
under development and ready to break it for constructive purpose.
The contents of the Test Strategy can be:
1. About the product/ feature in the words the tester understood.
2. Approach to derive test cases? Example: Derive test cases from
usecases which in turn are derived from requirements which were
written by the business analysts based on userinterviews and market
3. What will be verified? Example: return values, db tables, logfiles,
memory, etc. //Provide more details on what will be verified when.
4. Approach to Execute it faster: What tools he will be using to
5. Summary of the Test Results.
Any comments and additions are welcome.