Test strategy

ISTQB Glossary  definition 

"A high-level document defining the test levels to be performed and the testing within those levels for a programme (one or more projects)."

In Simple English,

It is a published agreement to keep all parties involved informed about the strategy defined to test a project. This involves documenting the level of testing targeted, the kinds of testing agreed on as needed and the approach agreed upon.

Field Notes 

1. This document is often confused with test plan document.

2. Depending on the way on organization defines it, test strategy sometimes will involve several items that are generally considered as part of a formal test plan.

3. Some companies altogether combine both the test strategy and test plan documents and have a single artifact. They call it Master test document or test strategy or test plan.
remember, as rose by any other name is still a rose.

4.This however is different from test policy. While Test Policy is defined and maintained at the organization level, test strategy is at a project or program level. (Program here does not mean a piece of code. It means a very big Project which in turn has several projects under it)


5. I have seen many test professionals obsess over the correct way to define this. Just remember that this is meant to be a tool to get the job done. it is just a means to an end, not the objective itself. what suits the organization and gets the job done is what is needed.

More important is to NOT pick a argument with someone in an effort to establish your view of test strategy.  It just does not matter as long as the project gets done and you are in compliance with what the client / organization wants.

6. Interviewers for some reason are far more obsessed with this than they should be. You should think about what the answer needs to be not what is the correct answer.
Think about it. :)


7. What needs to be tested and why it needs to be tested are usually the contents of this document. A general overview of How is included in cased where more details are known.

For Example:

Say you are asked "So Mr. / Miss. tester, how do you think we can get this software tested?" the answer you come up with is your test strategy.


So, what do you think?
Was the explanation clear enough?
Did you understand?
Did you get what you were searching for?

If you have any more questions, comments or compliments please let me know as your comments below.