Changes between Version 5 and Version 6 of TriagingTestFailures


Ignore:
Timestamp:
Nov 2, 2010 9:38:44 AM (10 years ago)
Author:
Adam Roben
Comment:

Address more of John Sullivan's feedback

Legend:

Unmodified
Added
Removed
Modified
  • TriagingTestFailures

    v5 v6  
    3131 * Use `svn log`/`git log` to find out when the test or its results were last changed
    3232
    33 = Try to figure out the reason each test is failing =
     33= Try to figure out why each test is failing =
    3434
    3535(You probably won't be able to figure out exactly why every test is failing, but the more information you can get now, the better.)
     
    7070 * If the tests fail every time and the tests' output is the same every time, check in new results for the tests and include the bug URL in your ChangeLog.
    7171   * You should do this even if the test is "failing". By running the test against these "expected failure" results rather than skipping the test entirely, we can discover when new regressions are introduced.
    72  * If the tests fail intermittently, or crash, or hang, add the tests to the appropriate Skipped files. Include a comment in the Skipped file with the bug URL and a brief description of how it fails (e.g., "Crashes", "Sometimes times out", etc.).
     72 * If the tests fail intermittently, or crash, or hang, add the tests 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.:
     73{{{
     74# Sometimes times out http://webkit.org/b/12345
     75fast/js/some-cool-test.html
     76}}}