As soon as you hear about a production bug in your product, the first thing you may want to do, is volunteer to log it.
- Multiple people may attempt to log the bug, which wastes time. Declare your offer to log it.
- You’re a tester. You can write a better bug report than others.
- It shows a willingness to jump in and assist as early as possible.
- It assigns the new bug an identifier, which aides conversation (e.g., “We think Bug1029 was created by the fix for Bug1028”).
- Now the team has a place to document and gather information to.
- Now you are intimately involved in the bug report. You should be able to grok the bug.
Shouldn’t I wait until I determine firm repro steps?
- No. Bug reports can be useful without repro steps. The benefits, above, do not depend on repro steps.
- No. If you need time to determine repro steps, just declare that in the bug report’s description (e.g., “repro steps not yet known, investigation under way”) and add them later.
But what if the programmer, who noticed the bug, understands it better than me? Wouldn’t they be in a better position to log the bug?
- Maybe. But you’re going to have to understand it sooner or later. How else can you test it?
- Wouldn’t you rather have your programmer’s time be spent fixing the code instead of writing a bug report?