Changes between Version 20 and Version 21 of TestExpectations


Ignore:
Timestamp:
Oct 9, 2012 12:01:27 AM (10 years ago)
Author:
pdr@google.com
Comment:

Fix spelling errors

Legend:

Unmodified
Added
Removed
Modified
  • TestExpectations

    v20 v21  
    4242* If no modifiers are specified, the test applies to all of the configurations applicable to that file
    4343* Modifiers can be one or more of `Mac`, `SnowLeopard`, `Lion`, `MountainLion`, `Win`, `XP`, `Vista`, `Win7`, `Win7SP0`, `Linux`, `Lucid`, `x86_64`, `x86`, `Release`, `Debug`. Not all modifiers make sense on all ports or in all lines.
    44 * Expectations can be one or more of `Crash`,  `Failure`, `ImageOnlyFailure`, `Pass`, `Rebaseline`, `Slow`, `Skip`, `Timeout`, `WontFix`. If mulitple expectations are listed, the test is considered "flaky" and any of those results will be considered as expected.
     44* Expectations can be one or more of `Crash`,  `Failure`, `ImageOnlyFailure`, `Pass`, `Rebaseline`, `Slow`, `Skip`, `Timeout`, `WontFix`. If multiple expectations are listed, the test is considered "flaky" and any of those results will be considered as expected.
    4545
    4646For example:
     
    110110     * throws JavaScript exception and makes text-only test manifest as pixel-test. This usually manifests in "Missing test expectations" failure.
    111111     * 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.
    112   * Try to specify platforms and configs as accurately as possible. If a test passes on all but on platform, it should only have that platform listed
     112  * 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
    113113  * If a test fails intermittently, use multiple expectations.