Changeset 90792 in webkit


Ignore:
Timestamp:
Jul 11, 2011 4:33:11 PM (13 years ago)
Author:
dpranke@chromium.org
Message:

update the boilerplate documentation in the test_expectations.txt files
​https://bugs.webkit.org/show_bug.cgi?id=64221

Reviewed by Eric Seidel.

The test expectations files either had documentation for the
Chromium port's version of the file (which was also incorrect),
or were undocumented. This adds a comment with a link to the
documentation for the file to each.

  • platform/chromium/test_expectations.txt:
  • platform/gtk/test_expectations.txt:
  • platform/mac/test_expectations.txt:
  • platform/qt/test_expectations.txt:
  • platform/win/test_expectations.txt:
Location:
trunk/LayoutTests
Files:
6 edited

Legend:

Unmodified
Added
Removed

  • trunk/LayoutTests/ChangeLog

    r90787 r90792  
     12011-07-11  Dirk Pranke  <dpranke@chromium.org>
     2
     3        update the boilerplate documentation in the test_expectations.txt files
     4        https://bugs.webkit.org/show_bug.cgi?id=64221
     5
     6        Reviewed by Eric Seidel.
     7
     8        The test expectations files either had documentation for the
     9        Chromium port's version of the file (which was also incorrect),
     10        or were undocumented. This adds a comment with a link to the
     11        documentation for the file to each.
     12
     13        * platform/chromium/test_expectations.txt:
     14        * platform/gtk/test_expectations.txt:
     15        * platform/mac/test_expectations.txt:
     16        * platform/qt/test_expectations.txt:
     17        * platform/win/test_expectations.txt:
     18
    1192011-07-11  Dirk Pranke  <dpranke@chromium.org>
    220

  • trunk/LayoutTests/platform/chromium/test_expectations.txt

    r90787 r90792  
    1 // This file consists of lines with specifications of what
    2 // to expect from layout test cases. The test cases can be directories
    3 // in which case the expectations apply to all test cases in that
    4 // directory and any subdirectory. The format of the file is along the
    5 // lines of:
     1// These are the layout test expectations for the Chromium port(s) of WebKit.
    62//
    7 // fast/js/fixme.js = FAIL
    8 // fast/js/flaky.js = FAIL PASS
    9 // fast/js/crash.js = CRASH TIMEOUT FAIL PASS
    10 //
    11 // The format of a test line is as follows:
    12 // METADATA : relative/path/to/test.html = EXPECTATIONS
    13 //
    14 // Valid values for METADATA:
    15 //
    16 // BUG(CR|WK|V8_)[0-9]+: See this chromium/webkit/v8 bug for more information.
    17 //                       Every test that isn't marked WONTFIX should have the
    18 //                       appropriate BUG annotation.
    19 // SKIP: Doesn't run the test.
    20 // SLOW: The test takes a long time to run, but does not timeout indefinitely.
    21 // WONTFIX: For tests that we never intend to pass on a given platform.
    22 // DEBUG: Expectations apply only to the debug build.
    23 // RELEASE: Expectations apply only to release build.
    24 // LINUX/WIN/XP/VISTA/MAC: Expectations apply only to these platforms.
    25 // GPU/CPU: Expectations only apply to a particular compositor. Default: both.
    26 //
    27 // Valid values for EXPECTATIONS:
    28 //
    29 // PASS: Test should pass
    30 // CRASH: Test should crash
    31 // TIMEOUT: Test should timeout
    32 // IMAGE: Test will produce an incorrect image dump
    33 // TEXT: Test will produce incorrect text output (either full or simplified)
    34 // IMAGE+TEXT: Test will produce both incorrect text and images
    35 // FAIL: Test will produce either incorrect text, images, or both
    36 //
    37 // If a line contains multiple expectations, it is considered "flakey",
    38 // because it means that we're not producing consistent, reliable results.
    39 //
    40 // For example,
    41 // LINUX : media = PASS FAIL
    42 //
    43 // The above means that all the media tests are flaky, but only on Linux.
    44 //
    45 // Other examples:
    46 //
    47 // SKIP : fast/js/no-good.js = TIMEOUT PASS
    48 // DEBUG : fast/js/no-good.js = TIMEOUT PASS
    49 // DEBUG SKIP : fast/js/no-good.js = TIMEOUT PASS
    50 // LINUX DEBUG SKIP : fast/js/no-good.js = TIMEOUT PASS
    51 // BUGCR1234 DEBUG MAC : fast/js/no-good.js = TIMEOUT PASS
    52 //
    53 // Notes:
    54 // -A test cannot be both SLOW and TIMEOUT
    55 // -A test can be included twice, but not via the same path.
    56 // -If a test is included twice, then the more precise path wins.
    57 // -CRASH tests cannot be WONTFIX
     3// See http://trac.webkit.org/wiki/TestExpectations for more information on this file.
    584
    595// -----------------------------------------------------------------

  • trunk/LayoutTests/platform/gtk/test_expectations.txt

    r57483 r90792  
     1// These are the layout test expectations for the GTK port of WebKit.
     2//
     3// See http://trac.webkit.org/wiki/TestExpectations for more information on this file.
     4

  • trunk/LayoutTests/platform/mac/test_expectations.txt

    r84998 r90792  
    1 // This file consists of lines with specifications of what
    2 // to expect from layout test cases. The test cases can be directories
    3 // in which case the expectations apply to all test cases in that
    4 // directory and any subdirectory. The format of the file is along the
    5 // lines of:
     1// These are the layout test expectations for Apple's Mac port of WebKit.
    62//
    7 // fast/js/fixme.js = FAIL
    8 // fast/js/flaky.js = FAIL PASS
    9 // fast/js/crash.js = CRASH TIMEOUT FAIL PASS
    10 //
    11 // The format of a test line is as follows:
    12 // METADATA : relative/path/to/test.html = EXPECTATIONS
    13 //
    14 // Valid values for METADATA:
    15 //
    16 // BUG(CR|WK|V8_)[0-9]+: See this chromium/webkit/v8 bug for more information.
    17 //                       Every test that isn't marked WONTFIX should have the
    18 //                       appropriate BUG annotation.
    19 // SKIP: Doesn't run the test.
    20 // SLOW: The test takes a long time to run, but does not timeout indefinitely.
    21 // DEFER: For tests we'll fix in the future.
    22 // WONTFIX: For tests that we never intend to pass on a given platform.
    23 // DEBUG: Expectations apply only to the debug build.
    24 // RELEASE: Expectations apply only to release build.
    25 // MAC/MAC-LEOPARD/MAC-TIGER/MAC-SNOWLEOPARD: Expectations apply only to
    26 //     these platforms.
    27 //
    28 // Valid values for EXPECTATIONS:
    29 //
    30 // PASS: Test should pass
    31 // CRASH: Test should crash
    32 // TIMEOUT: Test should timeout
    33 // IMAGE: Test will produce an incorrect image dump
    34 // TEXT: Test will produce incorrect text output (either full or simplified)
    35 // IMAGE+TEXT: Test will produce both incorrect text and images
    36 // FAIL: Test will produce either incorrect text, images, or both
    37 //
    38 // If a line contains multiple expectations, it is considered "flakey",
    39 // because it means that we're not producing consistent, reliable results.
    40 //
    41 // For example,
    42 // MAC : media = PASS FAIL
    43 //
    44 // The above means that all the media tests are flaky, but only on Linux.
    45 //
    46 // Other examples:
    47 //
    48 // SKIP : fast/js/no-good.js = TIMEOUT PASS
    49 // DEBUG : fast/js/no-good.js = TIMEOUT PASS
    50 // DEBUG SKIP : fast/js/no-good.js = TIMEOUT PASS
    51 // LINUX DEBUG SKIP : fast/js/no-good.js = TIMEOUT PASS
    52 // BUGCR1234 DEBUG MAC : fast/js/no-good.js = TIMEOUT PASS
    53 //
    54 // Notes:
    55 // -A test cannot be both SLOW and TIMEOUT
    56 // -A test can be included twice, but not via the same path.
    57 // -If a test is included twice, then the more precise path wins.
    58 // -CRASH tests cannot be WONTFIX
     3// See http://trac.webkit.org/wiki/TestExpectations for more information on this file.
    594
    605// Our slow tests, in alphabetical order.

  • trunk/LayoutTests/platform/qt/test_expectations.txt

    r90740 r90792  
    1 // This file consists of lines with specifications of what
    2 // to expect from layout test cases. The test cases can be directories
    3 // in which case the expectations apply to all test cases in that
    4 // directory and any subdirectory. The format of the file is along the
    5 // lines of:
     1// These are the layout test expectations for the QT port of WebKit.
    62//
    7 // fast/js/fixme.js = FAIL
    8 // fast/js/flaky.js = FAIL PASS
    9 // fast/js/crash.js = CRASH TIMEOUT FAIL PASS
    10 //
    11 // The format of a test line is as follows:
    12 // METADATA : relative/path/to/test.html = EXPECTATIONS
    13 //
    14 // Valid values for METADATA:
    15 //
    16 // BUG(CR|WK|V8_)[0-9]+: See this chromium/webkit/v8 bug for more information.
    17 //                       Every test that isn't marked WONTFIX should have the
    18 //                       appropriate BUG annotation.
    19 // SKIP: Doesn't run the test.
    20 // SLOW: The test takes a long time to run, but does not timeout indefinitely.
    21 // DEFER: For tests we'll fix in the future.
    22 // WONTFIX: For tests that we never intend to pass on a given platform.
    23 // DEBUG: Expectations apply only to the debug build.
    24 // RELEASE: Expectations apply only to release build.
    25 // MAC/MAC-LEOPARD/MAC-TIGER/MAC-SNOWLEOPARD: Expectations apply only to
    26 //     these platforms.
    27 //
    28 // Valid values for EXPECTATIONS:
    29 //
    30 // PASS: Test should pass
    31 // CRASH: Test should crash
    32 // TIMEOUT: Test should timeout
    33 // IMAGE: Test will produce an incorrect image dump
    34 // TEXT: Test will produce incorrect text output (either full or simplified)
    35 // IMAGE+TEXT: Test will produce both incorrect text and images
    36 // FAIL: Test will produce either incorrect text, images, or both
    37 //
    38 // If a line contains multiple expectations, it is considered "flakey",
    39 // because it means that we're not producing consistent, reliable results.
    40 //
    41 // For example,
    42 // MAC : media = PASS FAIL
    43 //
    44 // The above means that all the media tests are flaky, but only on Linux.
    45 //
    46 // Other examples:
    47 //
    48 // SKIP : fast/js/no-good.js = TIMEOUT PASS
    49 // DEBUG : fast/js/no-good.js = TIMEOUT PASS
    50 // DEBUG SKIP : fast/js/no-good.js = TIMEOUT PASS
    51 // LINUX DEBUG SKIP : fast/js/no-good.js = TIMEOUT PASS
    52 // BUGCR1234 DEBUG MAC : fast/js/no-good.js = TIMEOUT PASS
    53 //
    54 // Notes:
    55 // -A test cannot be both SLOW and TIMEOUT
    56 // -A test can be included twice, but not via the same path.
    57 // -If a test is included twice, then the more precise path wins.
    58 // -CRASH tests cannot be WONTFIX
     3// See http://trac.webkit.org/wiki/TestExpectations for more information on this file.
    594
    605BUGWK64002 : http/tests/misc/object-embedding-svg-delayed-size-negotiation-2.htm = TEXT PASS

  • trunk/LayoutTests/platform/win/test_expectations.txt

    r57434 r90792  
     1// These are the layout test expectations for Apple's Windows port of WebKit.
     2//
     3// See http://trac.webkit.org/wiki/TestExpectations for more information on this file.
     4
Note: See TracChangeset for help on using the changeset viewer.