Tuesday, 1 March 2011

me smash! me break!

I've been thinking about testing to make sure the bits that work actually work the way they should, testing the overall design, rather than just taking the 'me smash! me break!' testing approach.

In my experience, more testing and questioning of the spec before we get started vastly reduces the number of 'oh, we didn't think that bit through' occurences later on.

Unfortunately, it is not always easy as a tester to get in on the action at the spec stage, and we are often considered as an annoyance rather than a vital part of the team when we try to get involved. There are vague discussions about the spec, but nothing concrete, nothing written down, and then suddenly the software engineers have started coding, and yeah, the spec will be along in a bit.

So if anyone has any ideas about how to get in there sooner, and to be taken seriously at the concept stage, I would love some advice.


  1. Hi,

    Testers are not a welcome in early stages becoz we keep asking questions and finding issues with the spec. I suggest that we attend requirements/spec review meetings with a learning mindset and clearly let others know that we are juz learning the product not finding faults. Even if we do find issues, I would suggest not to open up immediately. Listen and learn quietly. Discuss about the product features with a learning attitude and the developers/architects/business analysts will continue having you in loop.
    After learning is done, reflect upon it and raise valid issues that really adds value to the business.

    "The intersection of Technology and Leadership"

  2. Thanks, Aruna. That's some good advice. I'll try that, and let you know how I get on. Thanks very much for your comment :)