824f4e083b
MozReview-Commit-ID: 1GaV7z8d0Xc --HG-- rename : testing/web-platform/tests/preload/link_header_preload_delay_onload.html.headers => testing/web-platform/tests/preload/link-header-preload-delay-onload.html.headers rename : testing/web-platform/tests/preload/link_header_preload.html.headers => testing/web-platform/tests/preload/link-header-preload.html.headers
1.2 KiB
| layout | title | order |
|---|---|---|
| page | Visual Tests | 7 |
Visual tests are typically used when testing rendering of things that cannot be tested with [reftests][].
Their main advantage of over manual tests is they can be verified using browser-specific and platform-specific screenshots; note, however, that many browser vendors treat them identically to manual tests hence they are similarly discouraged as they very infrequently, if ever, get run by them.
Writing a Visual Test
Visuals tests are test files which have -visual at the end of their
filename, before the extension. There is nothing needed in them to
make them work.
They should follow the [general test guidelines][general guidelines], especially noting the requirement to be self-describing (i.e., they must give a clear pass condition in their rendering).
Similarly, they should consider the [rendering test guidelines][rendering], especially those about color, to ensure those running the test don't incorrectly judge its result.
[general guidelines]: {{ site.baseurl }}{% link _writing-tests/general-guidelines.md %} [reftests]: {{ site.baseurl }}{% link _writing-tests/reftests.md %} [rendering]: {{ site.baseurl }}{% link _writing-tests/rendering.md %}