A strategy in its synonym is a preparation for long-term battle plans or making plans to achieve a goal. It might involve giving up a destructive habit or addiction or it might be a matter of recognizing a self-defeating pattern of behavior and somehow seeing how to change it.
For example the bulk of testing hours of a tester goes in to testing the product again and again for different releases in the same pattern. At a certain phase it leads to frustration of the testers for doing things repeatedly. It happens sometimes that when someone is frustrated he may sound something like, “I know its possible to see this (or experience) differently”. And often, this awareness or even hope that there is another way of experiencing your dilemma, or problem opens the door for it to occur. This is where strategies come in.
This 9 pages handbook contains the following topics:

1. Test Strategy
2. Why do we need a Test Strategy?
3. Avoiding the Risk
4. Establish Test Techniques
5. Software risk issues:

  • Features to Test
  • Features not Tested
  • Test Approach
  • Training Needs
  • Responsibilities
  • Planning Risk Contingencies

6. Conclusion


Download Link: Click Here 


I am sure this small handbook will help you in understanding and implementing the Testing Strategy. This document is prepared by Shiva Kumar from Think Network Solutions.