This isn't a blog post slagging off how developers (don't) test, it's also not about how testers should strive to create a quality culture and coach the team, and it's not about how clever I was at finding the problem either.
This blog post is about the response the developer gave when he heard my report: "what made you think to test it that way?"
Which is a great question from someone who wants to improve themselves and their work. I didn't want to put him off ever asking me anything ever again by taking the opportunity of an apparently receptive audience to lard on the testing know-how. So I said something along these lines:
There are basically two sides to testing a fix like this, and you need to look at both:
- checking for the intended effect
- looking for unintended consequences
When I'm testing I will often try to find ways of cheaply giving myself a chance to see unintended side-effects. In this case, it was to force the fix to be exercised lots of times on very little data. This makes the outcome easy to scan and problems easier to see, for example wrong results or missing application of the fix.
Source: ministry of testing
The Other Sides