Difference between revisions of "RAP Bug Reporting Howto"

Latest revision as of 12:34, 1 June 2012

@@ Line 1: / Line 1: @@
-This page explains how to write useful bug reports for RAP
+Moved to the [http://eclipse.org/rap/bugs/ RAP Bugs page]
-== Before you submit a bug ==
-=== Check whether it's working with SWT / RCP ===
-== Where to submit ==
-== What to Include in the Bug Report ==
-=== Bug Description ===
-The bug description should be as short and exact as possible.
-It should contain:
-* Your environment (operating system, browser type and version, RAP version)
-* The steps to reproduce the behavior described
-* The expected outcome / solution
-=== Provide a Code Snippet ===
-If the bug only occurs under certain circumstances, it's helpful if you can provide a snippet to reproduce.
-* The snippet should be as simple as possible.
-* The snippet should be self-contained (i.e. not rely on third-party code) and fit into one single class.
-* The snippet should be runnable without hacking, i.e. it should implement IEntryPoint.
-=== Provide a screenshot ===
-Remember that we don't have your exact desktop environment and browser.
-If you describe some visual misbehavior, a screenshot helps us understand your problem.
-The best image formats for screenshots is PNG or GIF.
-JPG is for photographs (is has lossy compression),
-uncompressed image formats like BMP, TIFF, etc. are just too big and take too long to download.