Changes between Version 4 and Version 5 of TriagingTestFailures


Ignore:
Timestamp:
Nov 2, 2010, 9:35:59 AM (14 years ago)
Author:
Adam Roben
Comment:

Address more of John Sullivan's feedback

Legend:

Unmodified
Added
Removed
Modified

  • TriagingTestFailures

    v4 v5  
    6868
    6969 * If you know what the root cause is, 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!
    70  * If the tests always fail with the same incorrect output, check in new results for the tests and include the bug URL in your ChangeLog.
     70 * 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.
    7272 * 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.).