reproduction d'une issue

http://www.softwaretestinghelp.com/how-to-write-good-bug-report

Reproduce the bug three times before writing bug report:Your bug should be reproducible. Make sure your steps are robust enough to reproduce the bug without any ambiguity. If your bug is not reproducible every time you can still file a bug mentioning the periodic nature of the bug.

http://blogs.msdn.com/johnguin/archive/2007/08/30/finding-an-easier-way-to-reproduce-a-bug.aspx

Minimal repro steps would have saved hours of time in this case (three testers, one customer, about two hours each to isolate) and could have resulted in a faster fix. So we will apply the lesson learned and use it for our future testing.

http://remstate.com/2008/01/06/squashing-bugs-intro-and-repros/

The first step in most bug-squashing efforts should be determining a consistent set of reproduction steps (known henceforth as a “repro”). Techniques are available for finding the cause of bugs that cannot be consistently reproduced, but it does tend to make life more difficult. When you make a repro produce the bug with more consistency, you reduce the number of real-world variables contributing to the cause, and increase the developer’s ability to track down and fix the problem. The bottom line is that you should strive to get the clearest and most consistent repro that you can.


As a tester performing ad-hoc testing, you should keep a mental stack of procedures you have performed. Be aware of as many things as possible when you are testing: things like mouse position, order of operations, if you performed an operation twice, and even the timing between operations, can all be factors in triggering a bug. If you do come across a bug in the program, start over from the last complete task you were attempting to perform. Try to replay that task in the same manner as you performed it before. If the bug does not repro the second time, start the task again and walk through the steps more carefully — try to recall anything different, unusual, or special that you did the first time that you encountered the bug. Repeat until you can either reproduce the bug, or convince yourself that you can’t find a working repro.


When you are given repros written by others, they may be incomplete, difficult to understand, or incorrect. If the bug was filed by a professional, simply direct them to the steps for a tester above. In other cases (such as with bugs filed by users), you will need to coax more information out of them. The best way to do this tends to be to have them attempt to reproduce the bug using their own instructions. If they insist that they can regularly reproduce the problem with their own steps, then send a tester to observe the repro firsthand if possible. If not, verify the consistency with them. If a user can consistently repro a problem, and you cannot, then there may be another issue at play.

http://books.google.com/books?id=-41OWKFiy1MC&printsec=frontcover#PPP1,M1