Software Testing Test Strategy

Test Strategy means how we plan to cover the product so as to develop an adequate assessment of quality.

Why do we need Test Strategy? The Test Strategy is the plan for how you are going to
approach testing. It is like a project charter that tells the world how you are going to approach the project. You may have it all in your head, and if you are the only person doing the work it might be OK. If however you do not have it all in your head, or if others will be involved, you need to map out the ground rules.

A good test strategy is:

- Specific

-Practical

- Justified

Test Approach and Test Architecture are other terms commonly used to describe what I’m calling test strategy.

Example of a poorly stated (and probably poorly conceived) test strategy:

"We will use black box testing, cause-effect graphing, boundary testing, and white box testing to test this product against its specification."