Changes between Version 10 and Version 11 of TriagingTestFailures

Timestamp:

Nov 3, 2010, 6:30:08 AM (14 years ago)

Author:

Adam Roben

Comment:

Note that the bug should be updated once you add the test to the Skipped file or check in new results

TriagingTestFailures

@@ -78 +78 @@
 
  * If you know why the test is failing, and know how to fix it (e.g., by making a change to WebKit or checking in new correct results), then fix it and close the bug!
- * If the test fails every time and the test's output is the same every time, check in new results for the test and include the bug URL in your ChangeLog.
-   * You should do this even if the test's output includes failure messages or incorrect rendering. By running the test against these "expected failure" results rather than skipping the test entirely, we can discover when new regressions are introduced.
- * If the test fails intermittently, or crashes, or hangs, add the test to the appropriate Skipped files (e.g., `LayoutTests/platform/mac-leopard/Skipped`). Include a comment in the Skipped file with the bug URL and a brief description of how it fails, e.g.:
+ * Otherwise, do one of the following and note what you did in the bug you filed.
+   * If the test fails every time and the test's output is the same every time, check in new results for the test and include the bug URL in your ChangeLog.
+     * You should do this even if the test's output includes failure messages or incorrect rendering. By running the test against these "expected failure" results rather than skipping the test entirely, we can discover when new regressions are introduced.
+   * If the test fails intermittently, or crashes, or hangs, add the test to the appropriate Skipped files (e.g., `LayoutTests/platform/mac-leopard/Skipped`). Include a comment in the Skipped file with the bug URL and a brief description of how it fails, e.g.:
 {{{
 # Sometimes times out http://webkit.org/b/12345