Changes between Version 12 and Version 13 of BugReporting


Ignore:
Timestamp:
2013-06-20 19:43:51 (7 years ago)
Author:
jeroens
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • BugReporting

    v12 v13  
    99 
    1010=== Best practices === 
    11 Reporting errors via a ticketing system such as Trac is quite a straight-forward process if you stick to a few simple rules. A good bug report ticket needs to have: 
     11Reporting errors via a ticketing system such as Trac is quite a straight-forward process if a few simple rules are kept in mind. A good bug report ticket needs to have: 
    1212 
    1313 1. A concise but informative title that explains the essence of the problem 
    1414 1. A list of steps explaining how to reproduce the bug 
    15  1. A sentence explaining what is expected to be seen 
    16  1. And lastly, a sentence on what was experienced instead of the expected behaviour 
    17  1. Optionally, if the ticket only appears using specific data sets, this data may have to be provided  
     15 1. Lastly, a sentence on what was experienced instead of the expected behaviour 
     16 1. Specific data may have to be attached to the ticket if the error only appears using that data  
    1817 
    1918An example for a reasonably good bug report is [http://sources.ecopath.org/trac/Ecopath/ticket/1240 ticket #1240].