commit | b026ab18693332fb5b9e860355488634994de80b | [log] [tgz] |
---|---|---|
author | Domenic Denicola <domenic@chromium.org> | Fri Aug 26 07:23:48 2022 |
committer | Blink WPT Bot <blink-w3c-test-autoroller@chromium.org> | Fri Aug 26 07:31:22 2022 |
tree | e520649fe1827cbcedacea34661ed07fde4fe908 | |
parent | d6795c56ae7421a02d484a37a60c1a44423322d6 [diff] |
Minor improvements to RemoteContext helper Some of these help with testing prerendering using the helper. * Allow the executorCreator option to createContext() to return a promise, which gets awaited. This allows it to consist of running script in another RemoteContextWrapper, e.g. to insert <script type=speculationrules>. (If it is sync, there is no change in behavior; it just waits an extra microtask.) Although previously you could still do async things in it and that would generally work (e.g. window creation via window.open() is essentially async), this change ensures any promise rejections are propagated. * Add a navigateTo() method to RemoteContextWrapper, to make some of the simpler cases where you would use navigate() easier. (Notably, this is what you would use for prerendering.) * Renamed addHtml() to addHTML(), following https://w3ctag.github.io/design-principles/#casing-rules. * Fixed cases where an executeScript() was not being awaited, notably in calls to navigate() or the navigation helpers, and in execution context creation. * Clean up a variety of confusing options passing and defaulting code and documentation. There was an overuse of null (instead of the JavaScript-idiomatic default of undefined) which caused optional argument forwarding to need to be manual. As part of this, also fixed up the documentation to denote optional arguments using the appropriate syntax, and to document options as object properties instead of documenting them as if they were arguments. * Other minor code and documentation cleanups Change-Id: I3d001f5921aa643e3c1d66d8e4e40b264c6636cc Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3841185 Reviewed-by: Fergal Daly <fergal@chromium.org> Commit-Queue: Domenic Denicola <domenic@chromium.org> Cr-Commit-Position: refs/heads/main@{#1039622}
The web-platform-tests Project is a cross-browser test suite for the Web-platform stack. Writing tests in a way that allows them to be run in all browsers gives browser projects confidence that they are shipping software that is compatible with other implementations, and that later implementations will be compatible with their implementations. This in turn gives Web authors/developers confidence that they can actually rely on the Web platform to deliver on the promise of working across browsers and devices without needing extra layers of abstraction to paper over the gaps left by specification editors and implementors.
The most important sources of information and activity are:
wpt:matrix.org
matrix channel; includes participants located around the world, but busiest during the European working day.If you'd like clarification about anything, don't hesitate to ask in the chat room or on the mailing list.
Clone or otherwise get https://github.com/web-platform-tests/wpt.
Note: because of the frequent creation and deletion of branches in this repo, it is recommended to “prune” stale branches when fetching updates, i.e. use git pull --prune
(or git fetch -p && git merge
).
See the documentation website and in particular the system setup for running tests locally.
The wpt
command provides a frontend to a variety of tools for working with and running web-platform-tests. Some of the most useful commands are:
wpt serve
- For starting the wpt http serverwpt run
- For running tests in a browserwpt lint
- For running the lint against all testswpt manifest
- For updating or generating a MANIFEST.json
test manifestwpt install
- For installing the latest release of a browser or webdriver server on the local machine.wpt serve-wave
- For starting the wpt http server and the WAVE test runner. For more details on how to use the WAVE test runner see the documentation.On Windows wpt
commands must be prefixed with python
or the path to the python binary (if python
is not in your %PATH%
).
python wpt [command]
Alternatively, you may also use Bash on Ubuntu on Windows in the Windows 10 Anniversary Update build, then access your windows partition from there to launch wpt
commands.
Please make sure git and your text editor do not automatically convert line endings, as it will cause lint errors. For git, please set git config core.autocrlf false
in your working tree.
The master branch is automatically synced to wpt.live and w3c-test.org.
Save the Web, Write Some Tests!
Absolutely everyone is welcome to contribute to test development. No test is too small or too simple, especially if it corresponds to something for which you've noted an interoperability bug in a browser.
The way to contribute is just as usual:
git checkout -b topic
../wpt lint
as described above.If you spot an issue with a test and are not comfortable providing a pull request per above to fix it, please file a new issue. Thank you!