Explaining how to report a bug
August 20, 2007 7:44 AM Subscribe
I'm having a few non-technical people test a webapp. What's the best one pager you've seen that explains the proper way to report a bug to a developer?
- What exactly did you do? What was the URL, what did you enter, etc.
- What exactly did you see? Exact output, not a paraphrase.
- What did you expect to see instead? (Some of the time this'll be a stupid question, when the behavior's an obvious error; much of the time it'll be relevant to identify just how the software violated the user's expectations.)
- Don't diagnose, just report the above.
posted by Zed_Lopez at 9:10 AM on August 20, 2007 [1 favorite]
I think the key point is to capture actual vs. expected results. For instance, here is the Apple bug format, some of which may be unneeded for you:
Summary:posted by smackfu at 9:13 AM on August 20, 2007
Provide a descriptive summary of the issue.
Steps to Reproduce:
In numbered format, detail the exact steps taken to produce the bug.
Expected Results:
Describe what you expected to happen when you executed the steps above.
Actual Results:
Explain what actually occurred when steps above are executed.
Regression:
Describe circumstances where the problem occurs or does not occur, such as software versions and/or hardware configurations.
Notes:
Provide additional information, such as references to related problems, workarounds and relevant attachments.
This is a bit over one page, but it is generally non-technical and easy to understand.
Zed_Lopez's advice is almost verbatim from a section of one of Joel Spolsky's essays on bug tracking. Most of that article is for the technically inclined, but it might be worth excerpting.
posted by indyz at 9:14 AM on August 20, 2007
Zed_Lopez's advice is almost verbatim from a section of one of Joel Spolsky's essays on bug tracking. Most of that article is for the technically inclined, but it might be worth excerpting.
posted by indyz at 9:14 AM on August 20, 2007
Oh, mrbugsentry: Getting an app to self-report things like crashes, database failures, etc. generally isn't difficult. Getting an app to report incorrect output, unexpected behavior ("I click on 'New Order' and it open the last order I was editing"), or matters of preference ("The input form is completely non-intuitive") can be anywhere from difficult to downright impossible.
posted by indyz at 9:18 AM on August 20, 2007
posted by indyz at 9:18 AM on August 20, 2007
Some excerpts from How To Ask Questions The Smart Way might help. In particular:
posted by mbrubeck at 9:20 AM on August 20, 2007
- Be precise and informative about your problem
- Describe the problem's symptoms, not your guesses
- Describe your problem's symptoms in chronological order
posted by mbrubeck at 9:20 AM on August 20, 2007
Yeah, I was cribbing from Spolsky. (I just didn't remember who I was cribbing from.)
posted by Zed_Lopez at 9:40 AM on August 20, 2007
posted by Zed_Lopez at 9:40 AM on August 20, 2007
« Older Will my permanent resident visa be transferred to... | Where to go in Venice and Florence? Newer »
This thread is closed to new comments.
posted by mrbugsentry at 8:08 AM on August 20, 2007