Changes between Version 29 and Version 30 of TestExpectations


Ignore:
Timestamp:
Feb 25, 2013 10:13:33 PM (9 years ago)
Author:
glenn@skynav.com
Comment:

editorial cleanup

Legend:

Unmodified
Added
Removed
Modified
  • TestExpectations

    v29 v30  
    111111== Rules of Thumb for Suppressing Failures ==
    112112
    113 Here are some rules-of-thumb that you could apply when adding new expectations to the file:
     113Here are some rules-of-thumb that you could apply when adding new expectations:
    114114
    115   * Only use WontFix when you know for sure we will never, ever implement the capability, tested by the test
    116   * Use Skip when the test:
    117      * throws JavaScript exception and makes text-only test manifest as pixel-test. This usually manifests in "Missing test expectations" failure.
    118      * disrupts running of the other tests. Although this is not typical, it may still be possible. Please make sure to give Pri-1 to the associated bug.
    119   * Try to specify platforms and configs as accurately as possible. If a test passes on all but one platform, it should only have that platform listed
     115  * Only use `WontFix` when you know for sure we will never, ever implement the capability tested by the test.
     116  * Use `Skip` when the test:
     117     * Throws a JavaScript exception and makes text-only test manifest as pixel-test. This usually manifests in a "Missing test expectations" failure.
     118     * Disrupts running of the other tests. Please make sure to assign Priority 1 to the associated bug.
     119  * Try to specify platforms and configurations as accurately as possible. If a test passes on all but one platform, it should only have that platform listed.
    120120  * If a test fails intermittently, use multiple expectations.