5 pts.
 When is Test Strategy document prepared?
When is Test Strategy document prepared? Is it prepared before or after test plan? How is it different from Test Plan ? What are contains of Test Strategy Document?

Software/Hardware used:
ASKED: March 31, 2010  6:55 AM
UPDATED: December 29, 2010  7:10 PM

Answer Wiki:
Test Plan: 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 Strategy. 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 observations. 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 execute? 5. Summary of the Test Results. Any comments and additions are welcome.
Last Wiki Answer Submitted:  June 25, 2010  5:45 am  by  Saimadhu   455 pts.
All Answer Wiki Contributors:  Saimadhu   455 pts.
To see all answers submitted to the Answer Wiki: View Answer History.


Discuss This Question:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _


 

We use test strategy document as the first step where we outline our strategy at a high level. This document is written at the planning stage when the requirements are in progress and have not been baselined.
Strategy document communicates to the team our high level plan/strategy for testing the product release.
Test plan is more indepth with details on all requirements, test coverage, risk ranking, etc.

 2,500 pts.