Mirrors/servo
1
0
Fork 0
mirror of https://github.com/servo/servo.git synced 2025-08-17 03:15:34 +01:00
Code Issues Projects Releases Packages Wiki Activity

Update web-platform-tests to revision 0ed072539aa45d3a5a67c9164b243d27873f257c

Browse source
This commit is contained in:
WPT Sync Bot 2019-12-13 08:23:34 +00:00
parent 0954871992
commit e613cfd108
76 changed files with 1109 additions and 703 deletions
Download patch file Download diff file Expand all files Collapse all files

22
tests/wpt/web-platform-tests/docs/writing-tests/crashtest.md Normal file
View file

@ -0,0 +1,22 @@
# crashtest tests
Crash tests are used to ensure that a document can be loaded without
crashing or experiencing other low-level issues that may be checked by
implementation-specific tooling (e.g. leaks, asserts, or sanitizer
failures).
Crashtests are identified by the string `-crash` in the filename, or
by being in a directory called `crashtests`.
The simplest crashtest is a single HTML file with any content. The
test passes if the load event is reached, and the browser finishes
painting, without terminating.
In some cases crashtests may need to perform work after the initial
page load. In this case the test may specify a `class=wait` attribute
on the root element. The test will not complete until that attribute
is removed from the root. At the time when the test would otherwise
have ended a `TestRendered` event is emitted; test authors can use
this event to perform modifications that are guaranteed not to be
batched with the initial paint. This matches the behaviour of
[reftests](reftests).

6
tests/wpt/web-platform-tests/docs/writing-tests/index.md
View file

@ -15,6 +15,7 @@ There's also a load of [general guidelines](general-guidelines) that apply to al
general-guidelines
ahem
assumptions
crashtest
css-metadata
css-user-styles
file-names
@ -63,6 +64,11 @@ expectations:
testing everything else. They are built with the testharness.js unit testing
framework, and consist of assertions written in JavaScript.
* [Crashtests](crashtest) tests are used to check that the browser is
able to load a given document without crashing or experiencing other
low-level issues (asserts, leaks, etc.). They pass if the load
completes without error.
* [wdspec](wdspec) tests are written in Python using
[pytest](https://docs.pytest.org/en/latest/) and test [the WebDriver browser
automation protocol](https://w3c.github.io/webdriver/)