"Testers like to find bugs". In that respect it sounds we've got a lot in common with entomologists.
The remit of a tester goes way beyond finding and studying bugs. One of which is preventing bugs. That probably might be one of the remits of an entomologist too? something to ponder over another time...
"Testers like to find bugs"; or do they ... ?
What is the fun of finding bugs? I've often asked myself that question. Pointing out to others the things that are not right. Always being the one in the team to draw the attention away from the good areas of a system or piece of software.
Well, that's one way of looking at it. Instead we could approach it from a different angle. Finding bugs should be a rewarding thing:
- It helps improving the quality of the product
- It helps saving money by limiting the amount of bugs to be fixed in production
- It helps your team to avoid introducing bugs
So, if "finding bugs is fun", We then can imply that "not finding bugs is not fun" (appologies for the double negative).
There must be some truth in that. Imagine if you're hired as a QA, and you don't find any bugs, that must be quite demoralising. Various emotions and reactions that can come into play:
- Self doubt - "Am I doing my job good enough?"
- Superfluous - "The quality of this product seems so good, I'm not needed here."
- Wasting time - "I put in all this effort with no tangible result."
Therefore, to get some job satisfaction, one must find bugs, right? And the more bugs you find, the more gratification you get as a reward? To a certain extent, definitely. But what if you find too many bugs? So many, that you get serious doubts about the level of expertise of your team members. Also that can be demoralising
Tester's satisfaction curve
And with that I present to you the Tester's Satisfaction Curve. This is not something I came up with. A good couple of years ago someone showed this to me, and it stuck, part from the source. If someone knows, please ping me, so I can do the author justice.
A tester's job satisfaction can be correlated to the amount of bugs it finds.
- A low number of bugs results in a low satisfaction
- With the number of bugs found increasing, so also does the tester's job satisfaction
- The satisfaction increase slows down with even more bugs found, till it reaches an optimum
- Then the gratification starts to drop with every additional bug found
This resonates with me, and have felt this in numerous situation throughout the years. Is this something you can relate to? Let me know (@peetronics).
Have joy finding bugs, but with moderation ...