Our greatest glory is not in never falling, but in rising every time we fall.
What do you do when your testing finds a program failure? Before you rush in headlong to debug it, step back and characterize the problem. This is especially important when you don't intend (or have no time) to repair it right away. Follow these steps to pin down the nature of the fault so that you, or any other developer, can come back later and attempt to sort it out.
Note what you were trying to do at the time and which actions triggered the failure.
Try it again. Discover whether the problem is repeatable, how frequently it crops up, and whether it coincides with any other activities going on at the same time.
Describe the fault. Fully. ...