mirror of
https://github.com/servo/servo.git
synced 2025-09-08 14:08:22 +01:00
Update web-platform-tests to revision 9659a35d816ff1b32835a2eccf3e0117dea4e5ce
This commit is contained in:
parent
6df0dc5b27
commit
4f0af2af66
54 changed files with 1873 additions and 137 deletions
|
@ -40,6 +40,9 @@ first two, and it is at times advisable to use testharness.js tests
|
|||
for things which would typically be tested using reftests but for
|
||||
which it would be overly cumbersome.
|
||||
|
||||
See [file names][] for test types and features determined by the file names,
|
||||
and [server features][] for advanced testing features.
|
||||
|
||||
In addition to the four main test types, there are also WebDriver
|
||||
tests, which are used exclusively for testing the WebDriver protocol
|
||||
itself. There is currently no documentation about these tests,
|
||||
|
@ -52,8 +55,10 @@ the [typical GitHub Pull Request workflow][submission-process]; please
|
|||
make sure you run the [`lint` script][lint-tool] before opening a pull request!
|
||||
|
||||
[introduction]: {{ site.baseurl }}{% link introduction.md %}
|
||||
[file names]: {{ site.baseurl }}{% link _writing-tests/file-names.md %}
|
||||
[general guidelines]: {{ site.baseurl }}{% link _writing-tests/general-guidelines.md %}
|
||||
[reftests]: {{ site.baseurl }}{% link _writing-tests/reftests.md %}
|
||||
[server features]: {{ site.baseurl }}{% link _writing-tests/server-features.md %}
|
||||
[testharness.js]: {{ site.baseurl }}{% link _writing-tests/testharness.md %}
|
||||
[visual]: {{ site.baseurl }}{% link _writing-tests/visual.md %}
|
||||
[manual]: {{ site.baseurl }}{% link _writing-tests/manual.md %}
|
||||
|
|
|
@ -8,8 +8,8 @@ order: 12
|
|||
|
||||
Certain test scenarios require more than just static HTML
|
||||
generation. This is supported through the
|
||||
[wptserve](http://wptserve.readthedocs.io) server. Several scenarios
|
||||
in particular are common:
|
||||
[wptserve](http://wptserve.readthedocs.io) server, and controlled by
|
||||
[file name flags][file names]. Several scenarios in particular are common:
|
||||
|
||||
|
||||
### Tests Involving Multiple Origins
|
||||
|
@ -85,3 +85,6 @@ responses. It also provides the ability to write Python scripts that
|
|||
have access to request data and can manipulate the content and timing
|
||||
of the response. For details see the
|
||||
[wptserve documentation](https://wptserve.readthedocs.org).
|
||||
|
||||
|
||||
[file names]: {{ site.baseurl }}{% link _writing-tests/file-names.md %}
|
||||
|
|
|
@ -16,8 +16,8 @@ documented in two sections:
|
|||
* [idlharness.js Documentation][idlharness] — A library for testing
|
||||
IDL interfaces using `testharness.js`.
|
||||
|
||||
As always, we recommend reading over the [general guidelines][] for
|
||||
all test types.
|
||||
See [server features][] for advanced testing features that are commonly used
|
||||
with testharness.js. See also the [general guidelines][] for all test types.
|
||||
|
||||
## Auto-generated test boilerplate
|
||||
|
||||
|
@ -103,3 +103,4 @@ Use `// META: timeout=long` at the beginning of the resource.
|
|||
[general guidelines]: {{ site.baseurl }}{% link _writing-tests/general-guidelines.md %}
|
||||
[testharness-api]: {{ site.baseurl }}{% link _writing-tests/testharness-api.md %}
|
||||
[idlharness]: {{ site.baseurl }}{% link _writing-tests/idlharness.md %}
|
||||
[server features]: {{ site.baseurl }}{% link _writing-tests/server-features.md %}
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue