SEPTEMBER 20, 2018

Why I Prefer Good Testing Over Excellent Testing – Part 7

This is the seventh (and final) article in a series that expands on a talk I've given called "Why I Prefer Good Testing Over Excellent Testing".

Summary of Story Time

In the past 5 articles, I've shared stories about defects I missed that I wouldn't have found with all the time in the world, and cases where I was saved by good monitoring and roll-back strategies. To summarize the key lessons I learned:

Ultimately, doing really excellent testing before releasing our work would not have helped in any of the situations I described.

How do I make "good testing" work for me?

So hopefully by now you’re thinking, this all sounds great, but how would I get started doing this in my own team? Well, the first step (not surprisingly) is to do good testing.

1. Do Good Testing

Then, instead of continuing to test further, invest the rest of your time in planning for failure. Here are some questions you could ask yourself to get started.

2. Plan For Failure

These are just a few suggestions for brainstorming your failure planning - there are lots more things you could consider and ask about, but this list should at least be a good place to get started.

What does all this mean for me and my team?

So, let’s say you’ve decided to try “good testing” in combination with detailed failure planning. How will this change the way you and your team operate?

Changes in Focus
Changes in Expectations
Changes in Success Criteria

Closing Thoughts

In closing, if we boil this entire series of articles down to just one sentence, the key piece of advice I am offering is: it's a good idea to be ready to handle failure, because in all likelihood you're not going to find all the bugs anyway :)

, TF