BugReporting
On 14 Nov in the Lahore office, we brainstormed a set of procedures community and dev should follow to to make the bug reporting process smoother for everyone.
WikiEditors
Here is what content/community should do when reporting bugs:
- Include all relevant information.
- What actions did you take?
- What should have happened?
- What actually happened?
- Is this bug reproducible? Does it show up on all pages or some pages? Make some (but not too much) effort to see if you can reproduce it again in other places. If it's not easy to reproduce, let us know how often you tend to see it happen.
- Let us know why this bug is important to fix.
- Let us know how the bug should be prioritized relative to other issues. If the bug has high priority, email Jon Farr and/or let the dev team know in person.
- If a bug isn't getting the attention you feel it deserves, bother the dev team.
Dev team
- Leave feedback on the status of the bug. Leave notes explaining:
- If you're not sure what the issue is, but have looked into it.
- If you've discovered the cause of the bug, and evaluated what it would take to fix it.
- If you're working on a fix.
- If the fix is stuck on some other bug/feature you have less control over.
- If you're not fixing the bug, leave a note explaining why not. Explain if this bug is going to be fixed as part of replacing/removing some existing code. Explain if other things are higher priority. Every bug deserves either to be fixed or an explanation why it hasn't been yet.
- Announce when you've fixed the bug, both by delivering the bug and letting any relevant parties know.
Professional Testing
It might be useful to understand what would be expected of a professional tester engaged in dialog with development. Testing guru Cem Kaner calls this Bug Advocacy, a process that he explains in detail in this video:
