怎样高效地报告Bug

Summary

• The first aim of a bug report is to let the programmer see the failure with their own eyes. If you can't be with them to make it fail in front of them, give them detailed instructions so that they can make it fail for themselves.
• In case the first aim doesn't succeed, and the programmer can't see it failing themselves, the second aim of a bug report is to describe what went wrong. Describe everything in detail. State what you saw, and also state what you expected to see. Write down the error messages, especially if they have numbers in.
• When your computer does something unexpected, freeze. Do nothing until you're calm, and don't do anything that you think might be dangerous.
• By all means try to diagnose the fault yourself if you think you can, but if you do, you should still report the symptoms as well.
• Be ready to provide extra information if the programmer needs it. If they didn't need it, they wouldn't be asking for it. They aren't being deliberately awkward. Have version numbers at your fingertips, because they will probably be needed.
• Write clearly. Say what you mean, and make sure it can't be misinterpreted.
• Above all, be precise. Programmers like precision.

　　作者想要传授的技巧简单说来就只有“详细”两个字，我们能够准确地描述出问题所在，程序开发者们才能有更多的精力去解决Bug而不是寻找Bug。

 

　　https://www.chiark.greenend.org.uk/~sgtatham/bugs.html

转载于:https://www.cnblogs.com/AbsolutelyPerfect/p/8452075.html