OLD | NEW |
1 # Layout Tests | 1 # Layout Tests |
2 | 2 |
3 Layout tests are used by Blink to test many components, including but not | 3 Layout tests are used by Blink to test many components, including but not |
4 limited to layout and rendering. In general, layout tests involve loading pages | 4 limited to layout and rendering. In general, layout tests involve loading pages |
5 in a test renderer (`content_shell`) and comparing the rendered output or | 5 in a test renderer (`content_shell`) and comparing the rendered output or |
6 JavaScript output against an expected output file. | 6 JavaScript output against an expected output file. |
7 | 7 |
8 This document covers running and debugging existing layout tests. See the | 8 This document covers running and debugging existing layout tests. See the |
9 [Writing Layout Tests documentation](./writing_layout_tests.md) if you find | 9 [Writing Layout Tests documentation](./writing_layout_tests.md) if you find |
10 yourself writing layout tests. | 10 yourself writing layout tests. |
(...skipping 446 matching lines...) Expand 10 before | Expand all | Expand 10 after Loading... |
457 The above command will generate a new baseline for | 457 The above command will generate a new baseline for |
458 `LayoutTests/foo/bar/test.html` and put the output files in the right place, | 458 `LayoutTests/foo/bar/test.html` and put the output files in the right place, |
459 e.g. | 459 e.g. |
460 `LayoutTests/platform/chromium-win/LayoutTests/foo/bar/test-expected.{txt,png,ch
ecksum}`. | 460 `LayoutTests/platform/chromium-win/LayoutTests/foo/bar/test-expected.{txt,png,ch
ecksum}`. |
461 | 461 |
462 When you rebaseline a test, make sure your commit description explains why the | 462 When you rebaseline a test, make sure your commit description explains why the |
463 test is being re-baselined. If this is a special case (i.e., something we've | 463 test is being re-baselined. If this is a special case (i.e., something we've |
464 decided to be different with upstream), please put a README file next to the new | 464 decided to be different with upstream), please put a README file next to the new |
465 expected output explaining the difference. | 465 expected output explaining the difference. |
466 | 466 |
467 ## W3C Tests | 467 ## Web Platform Tests |
468 | 468 |
469 In addition to layout tests developed and run just by the Blink team, there are | 469 In addition to layout tests developed and run just by the Blink team, there is |
470 also W3C conformance tests. For more info, see | 470 also a shared test suite, see [Web Platform Tests](./web_platform_tests.md). |
471 [Importing the W3C Tests](https://www.chromium.org/blink/importing-the-w3c-tests
). | |
472 | 471 |
473 ## Known Issues | 472 ## Known Issues |
474 | 473 |
475 See | 474 See |
476 [bugs with the component Blink>Infra](https://bugs.chromium.org/p/chromium/issue
s/list?can=2&q=component%3ABlink%3EInfra) | 475 [bugs with the component Blink>Infra](https://bugs.chromium.org/p/chromium/issue
s/list?can=2&q=component%3ABlink%3EInfra) |
477 for issues related to Blink tools, include the layout test runner. | 476 for issues related to Blink tools, include the layout test runner. |
478 | 477 |
479 * Windows and Linux: Do not copy and paste while the layout tests are running, | 478 * Windows and Linux: Do not copy and paste while the layout tests are running, |
480 as it may interfere with the editing/pasteboard and other clipboard-related | 479 as it may interfere with the editing/pasteboard and other clipboard-related |
481 tests. (Mac tests swizzle NSClipboard to avoid any conflicts). | 480 tests. (Mac tests swizzle NSClipboard to avoid any conflicts). |
482 * If QuickTime is not installed, the plugin tests | 481 * If QuickTime is not installed, the plugin tests |
483 `fast/dom/object-embed-plugin-scripting.html` and | 482 `fast/dom/object-embed-plugin-scripting.html` and |
484 `plugins/embed-attributes-setting.html` are expected to fail. | 483 `plugins/embed-attributes-setting.html` are expected to fail. |
OLD | NEW |