Did you even hear about testing syndrome?

Maybe not, because I just came up with this to describe two of the most common things that happen when it comes test strategies:

1. testing without a strategy. Then complaining for not having enough time to test everything.

2. the person who writes the strategy has absolutely no imagination – 2 or 3 pages written in a rush and he/she calls that a strategy.

Good testing starts with a good strategy.


Not this kind though:)))

Here are a few tips when writing such a document:

Be creative, think about what would the readers like to see in your document.

I know from experience that business users are very visual and don’t like to read stuff, so the more visual you make it the better it is. Other people like Excel spreadsheets or Powerpoint presentations, try to accomodate more styles within the same document.

Use color, tables, different styles of fonts, Visio diagrams to break the boredom of the plain text.

When I open a document that has small fonts or pages and pages of plain black on white text I just take a deep breath and try to follow the lines. As I exhale, I’m concentrating to read. I give up after I read one page (I am exaggerating, of course, but you get my point).

Organize your information ahead, don’t just dump everything in the strategy at the first thought.

Present it in a logical sequence, for example you want to start the Testing Approach section with an overview, then go slowly into details and finish with a short conclusion.

Depending how well your audience is trained in testing you may want to give more or less details about testing basics.

I find that in some cases, it’s not only the senior QA people who will review the strategy, but also junior testers, project managers, or business users, and they may not be familiar with all the testing terminology and common practice.

Exercise caution if you’re using a template, as there may be sections that are missing or not applicable. In this case, I suggest use the company’s template, but customize it to suit your needs. Include sections that you think are important for your project.

I will post a Test Strategy template in the Free downloads page.

Photo credits: Tim Caynes on – Thanks!


Other posts you may also like:

Medspeak, Bankspeak, Testspeak

What is worse: having badly written requirements or no requirements

Should users be involved in testing?

See an example of a test execution report


  1. Pingback: Brainsick Patterns — No Code Relation » Blog Archive » I often forget that an idea should start on paper

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s