How to write a good bug report: Difference between revisions

From MoodleDocs
No edit summary
(Redirected page to dev:Tracker introduction)
 
(2 intermediate revisions by one other user not shown)
Line 1: Line 1:
A good starting point would be the [[http://developer.mozilla.org/en/docs/Bug_writing_guidelines mozilla bug writing guidelines]].
#REDIRECT [[dev:Tracker_introduction]]
 
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).

Latest revision as of 07:40, 3 August 2012