转载
原文链接：http://www.51testing.com/html/68/85168-1297.html
Useful bug reports are ones that get bugs fixed. A useful bug report normally has two qualities:
1.Reproducible（可重现的）. If an engineer can't see the bug herself to prove that it exists, she'll probably stamp your bug report "WORKSFORME" or "INVALID"（无效的） and move on to the next bug. Every detail you can provide helps.
2.Specific（明确的）. The quicker the engineer can isolate the bug to a specific area, the more likely she'll expediently（方便地） fix it. (If a programmer or tester has to decipher（辨认） a bug, they may spend more time cursing(诅咒) the submitter than solving the problem.)
Descrīption（描述）: Please provide a detailed problem report in this field. Your bug's recipients（接收人） will most likely expect the following information:
Overview Descrīption:More detailed expansion of summary.
-Drag-selecting（拖拽选择） any page crashes Mac builds in NSGetFactory
Steps to Reproduce:Minimized, easy-to-follow（易于遵循） steps that will trigger the bug. Include any special setup steps（特殊的安装步骤）.
1) View any web page. (I used the default（默认的） sample（样本） page,
resource:/res/samples/test0.html)
2) Drag-select the page. (Specifically, while holding down
the mouse button, drag the mouse pointer downwards from any
point in the browser's content region（区域） to the bottom of the
browser's content region.)
Actual Results（预期结果）:What the application did after performing the above steps.
-The application crashed. Stack crawl appended below from MacsBug.
Expected Results（实际结果）:What the application should have done, were the bug not present.
-The window should scroll downwards. Scrolled content should be selected. (Or, at least, the application should not crash.)
Build Date & Platform（创建日期和平台）:Date and platform. of the build that you first encountered（遇到） the bug in.
-Build 2002-03-15 on Mac OS 9.0
