If it doesn’t work in production, was it badly tested? Or, is it that testing – like use in production – shows problems that were already there, but without trying them early on, the problems remain in production?
This presentation deals with the biggest learning over the years as tester that I’ve needed to pick up: while it’s great that I’m useful and needed, I need to actively work towards being less needed by teaching more testing skills to all team members and always remember that the quality belongs with the developer. It was already broken, I did not break it, and learning to break it less is a valuable thing developers pick up with testing skills.
We look at an example of a team that, learning to rely on the tester, ended up with worse quality than without a tester. We’ll also look at the practical steps of assigning responsibilities and pairing up and test automation effort that helped bring things back in balance.