How to write a good bug report: diferència entre les revisions
De MoodleDocs
Cap resum de modificació |
Cap resum de modificació |
||
Línia 10: | Línia 10: | ||
Preliminaries: | Preliminaries: | ||
1. | 1. Reproduce your bug using a recent build of the software, to see whether it has already been fixed. | ||
2. Search moodle bug tracker, to see whether your bug has already been reported (sometimes might be tricky). | 2. Search moodle bug tracker, to see whether your bug has already been reported (sometimes might be tricky). |
Revisió del 09:55, 20 feb 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:
1. Reproduce your bug using a recent build of the software, to see whether it has already been fixed. 2. Search moodle bug tracker, to see whether your bug has already been reported (sometimes might be tricky).