This is a mobile version, full one is here.
24 April 2018
The Right Way to Report a Bug
You know, at Zerocracy, either you are a programmer or a tester, and we pay for each bug you find and report. Well, not quite. We pay for each bug report a project architect considers good enough to pay for. The architect's decision is totally subjective and non-disputable, according to §29 of the Policy. Some of our developers find this unfair and ask me to explain how they can report bugs such that they are definitely paid. Here is a non-exhaustive list of my recommendations.
To be honest, there are many articles written before on this very subject. I will try not to repeat them. They mostly say reasonable things, like "be specific," "choose a strong title," "avoid duplicates," and many others. My recommendations here are more of a psychological nature.
Stay cool. Don't expect all of your bugs to be accepted and paid for. Some of them won't be. This must not stop you from reporting them.
Exaggerate. No matter how minor the bug is, present it as if the entire world will collapse tomorrow if they don't fix it. Of course, they will make their own decision about the priority and severity of the bug, but don't help them to make it against you.
Victimize yourself. Don't just say "the class is broken"—there is no victim in this statement. So, no need to save anyone's life. The bug is minor—no need to pay. Instead, say "I can't use the class." Present yourself as a victim. Or even better, represent a group of victims: "Nobody can really use this class."
Push them. If a bug report is not paid for, don't hesitate to ask why. Insist that it was a very important problem and you deserve to be paid. If they still don't pay, forget it and move on. You must not look like it offends you somehow.
Show efforts. The bug description must look "rich," clearly demonstrating that you invested a lot of effort in its creation. If there is just a single line, it's easier for them to not pay you—they won't feel any guilt. However, if it's long, detailed, properly formatted, and contains multiple supporting links, they will feel bad if they don't pay.
Look engaged. Say something like "I'm ready to investigate more and provide additional details, if you need me too." Of course you won't do that (in most cases), but you have to say it. This will look like you care and this bug comes right from your heart. How can they not pay for it?
Look altruistic. Don't show them that you are reporting these bugs just to get money. They know that anyway, but still. Look like you care about the project and honestly want to help. Say that you worry about the users, about the market, about the mission, about the bigger scope, etc.
Aggregate. This may sound against the principles of bug tracking I suggested earlier, but when your bugs are small and cosmetic—aggregate them. In such a case you have a chance to win. They will reject three minor bugs, but they won't reject a bigger one with three minor parts.
I believe that if you follow these simple recommendations, you will be a more successful bug reporter. At least at Zerocracy.