Mirrors/servo
1
0
Fork 0
mirror of https://github.com/servo/servo.git synced 2025-08-14 09:55:35 +01:00
Code Issues Projects Releases Packages Wiki Activity

Update web-platform-tests to revision bc60e6f82132cfc9a5b688c566c7772024b3c15c

Browse source
This commit is contained in:
WPT Sync Bot 2019-07-26 10:25:50 +00:00
parent 449881f566
commit 29156ca9e2
223 changed files with 7517 additions and 2093 deletions
Download patch file Download diff file Expand all files Collapse all files

24
tests/wpt/web-platform-tests/docs/writing-tests/general-guidelines.md
View file

@ -37,11 +37,10 @@ on [file names][file-name-flags].
#### Support Files
Various support files are available in in the `/common/` and `/media/`
directories (web-platform-tests) and `/support/` (in css/). Reusing
existing resources is encouraged where possible, as is adding
generally useful files to these common areas rather than to specific
test suites.
Various support files are available in in the directories named `/common/`,
`/media/`, and `/css/support/`. Reusing existing resources is encouraged where
possible, as is adding generally-useful files to these common areas rather than
to specific test suites.
#### Tools
@ -61,9 +60,17 @@ subdirectory and put your script there.
### File Formats
Tests must be HTML or XML (inc. XHTML and SVG) files; some
testharness.js tests
are [auto-generated from JS files][server features].
Tests are generally formatted as HTML (including XHTML) or XML (including SVG).
Some test types support other formats:
- [testharness.js tests](testharness) may be expressed as JavaScript files
([the WPT server automatically generates the HTML documents for these][server
features])
- [WebDriver specification tests](wdspec) are expressed as Python files
The best way to determine how to format a new test is to look at how similar
tests have been formatted. You can also ask for advice in [the project's IRC
room][IRC].
### Character Encoding
@ -179,6 +186,7 @@ for CSS have some additional requirements for:
[server features]: server-features
[assumptions]: assumptions
[ahem]: ahem
[IRC]: irc://irc.w3.org:6667/testing
[lint-tool]: lint-tool
[css-metadata]: css-metadata
[css-user-styles]: css-user-styles

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

@ -5,10 +5,6 @@ these are especially using for [visual](visual) tests which need to be manually
judged and following common patterns makes it easier to correctly tell if a
given test passed or not.
## Make tests self-describing
Tests should make it obvious when they pass and when they fail. It shouldn't be necessary to consult the specification to figure out whether a test has passed of failed.
## Indicating success
Success is largely indicated by the color green; typically in one of
@ -80,7 +76,7 @@ ways:
* Silver or light gray is often used for irrelevant content, such as
filler text.
Obviously, none of this can be taken as absolute rules, as testing of
None of these rules are absolute because testing
color-related functionality will necessitate using some of these
colors!