How to write a good bug report: Difference between revisions
From MoodleDocs
No edit summary |
No edit summary |
||
| (3 intermediate revisions by the same user not shown) | |||
| Line 10: | Line 10: | ||
Preliminaries: | Preliminaries: | ||
* Reproduce your bug using a recent build of the software, to see whether it has already been fixed. | |||
* Search moodle bug tracker, to see whether your bug has already been reported (sometimes might be tricky). | |||
Latest revision as of 09:56, 20 February 2008
A good starting point would be the [mozilla bug writing guidelines].
Here are some basic principles:
- Be precise
- Be clear - explain it so others can reproduce the bug
- One bug per report
- No bug is too trivial to report - small bugs may hide big bugs
- Clearly separate fact from speculation
Preliminaries:
- Reproduce your bug using a recent build of the software, to see whether it has already been fixed.
- Search moodle bug tracker, to see whether your bug has already been reported (sometimes might be tricky).
