Anonymous user
Open Source Comes to Campus/Newcomer Tasks/Issue Tracker Cleaning: Difference between revisions
Open Source Comes to Campus/Newcomer Tasks/Issue Tracker Cleaning (view source)
Revision as of 20:19, 29 July 2014
, 9 years agono edit summary
No edit summary |
No edit summary |
||
Line 12:
== Reproducing Bugs ==
To find bugs to reproduce, look through the issue tracker. You may want to filter the issues you see so that you're only looking for "new", "unconfirmed" or "open" issues.)
Once you've found a bug report, you'll want to try to reproduce it. You will find yourself in one of three scenarios:
Line 40:
<blockquote>Thanks for reporting this bug! Can you tell us which version of the project you found the bug in, and which operating system and version number you're using?</blockquote>
==== The Bug Is Reproducible ====
If you can reproduce the bug, leave a comment which:
* Says that you can reproduce the bug.
* Re-states what you expected to happen, and what actually happened.
* Goes over the steps you took to reproduce the problem. This should be as detailed as possible, including the commands you ran, input you supplied, and any output you got back.
** If you're up for it (and if it's relevant) attach a short, standalone program that reproduces the bug and add it to the ticket. This will be a helpful basis for writing test cases.
* List all versions of project in which the bug was and wasn't present for you.
* List all operating systems on which the bug was and wasn't present for you.
| |||