JA/QA/bug-writing

これは、LibreOfficeバグ報告システムにあるBug Writing(バグの書き方)の翻訳です.

効果的なバグ報告をすると、修正される可能性はとても高くなります. このガイドラインでは、そうしたレポートの書き方を説明します.

原則

 * 正確であること
 * 明確であること - 他の人がバグを再現できるように説明する
 * 1件の報告には1つのバグ
 * 報告しなくていいバグはありません - 小さなバグは大きなバグを隠している可能性があります
 * 事実と推測を明確に分ける

準備

 * 1) バグを最新のビルドを使って再現して、すでに修正されているか確認します.
 * 2) Bugzillaを検索して、バグがすでに報告されているか確認します.

新しいバグの報告
バグが最新のビルドで再現され、誰も報告していないようであれば以下の手順で報告をしてください:


 * 1) File a Bug(バグをファイルする)を選択する.
 * 2) バグが見つかった製品名を選択する.  (LibreOfficeを選びます. Impress RemoteやLibreOffice Onlineなどは、それぞれ選びます)
 * 3) フォームに記入する. 以下にそれを理解するためのの解説があります:

Component: In which sub-part of the software does it exist?

This field is required. Click the word &quot;Component&quot; to see a description of each component. If none seems appropriate, look for a &quot;General&quot; component.

OS: On which operating system (OS) did you find it? (e.g. Linux, Windows XP, Mac OS X.)

If you know the bug happens on more than one type of operating system, choose All. If your OS isn't listed, choose Other.

Summary: How would you describe the bug, in approximately 60 or fewer characters?

A good summary should quickly and uniquely identify a bug report. It should explain the problem, not your suggested solution.


 * Good: &quot;Cancelling a File Copy dialog crashes File Manager&quot;
 * Bad: &quot;Software crashes&quot;
 * Bad: &quot;Browser should work with my web site&quot;

Description: The details of your problem report, including:

Overview: More detailed restatement of summary.

"Drag-selecting any page crashes Mac builds in the NSGetFactory function." 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." 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 &amp; Hardware: Date and hardware of the build in which you first encountered the bug.

"Build 2006-08-10 on Mac OS 10.4.3" Additional Builds and Platforms: Whether or not the bug takes place on other platforms (or browsers, if applicable).

"Doesn't Occur On Build 2006-08-10 on Windows XP Home (Service Pack 2)" Additional Information: Any other useful information.

For crashing bugs:

Double-check your report for errors and omissions, then press &quot;Commit&quot;. Your bug report will now be in the Bugzilla database.
 * Windows: Note the type of the crash, and the module that the application crashed in (e.g. access violation in apprunner.exe).
 * Mac OS X: Attach the &quot;Crash Reporter&quot; log that appears upon crash. Only include the section directly below the crashing thread, usually titled &quot;Thread 0 Crashed&quot;. Please do not paste the entire log!