How to write a good bug report: Difference between revisions
From MoodleDocs
No edit summary |
No edit summary |
||
Line 1: | Line 1: | ||
A good starting point would be the [[http://developer.mozilla.org/en/docs/Bug_writing_guidelines mozilla bug writing guidelines]] | A good starting point would be the [[http://developer.mozilla.org/en/docs/Bug_writing_guidelines 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: | |||
============== |
Revision as of 23:50, 19 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: