| commit | 92648882a85510deb007b0e36cf766b9651c8cb5 | [log] [tgz] |
|---|---|---|
| author | David Van Cleve <davidvc@chromium.org> | Thu Apr 16 02:13:02 2020 |
| committer | Blink WPT Bot <blink-w3c-test-autoroller@chromium.org> | Thu Apr 16 02:42:26 2020 |
| tree | 7bf20af9e0beff52c93e48e0a9066233957496c2 | |
| parent | edb59b8bc77dc941ae589b8210e089e874034d98 [diff] |
Trust Tokens: Add TestRunner support for state reset and key commitments The prototype Trust Token API (https://github.com/wicg/trust-token-api) provides new JS functionality with which one can specify certain cryptographic operations to execute along outgoing requests. These operations can affect persistent state stored in the network service, so tests exercising them would be non-hermetic absent additional functionality to reset the state. Additionally, the operations rely on the presence of "key commitments" (collections of cryptographic keys and associated metadata) obtained through the component updater in standard operation; tests need a way to set these keys without relying on the updater. This CL adds testRunner bindings to 1. reset persistent Trust Tokens state and 2. manually set Trust Tokens key commitments so that it's possible to write end-to-end Blink layout tests for the new Trust Tokens functionality. Eventually, the same functionality will likely become available through WPT testdriver, and the Trust Tokens tests will be able to migrate to WPT: since it's slightly more involved to implement equivalent functionality via testdriver, this is a first pass allowing writing end-to-end HTML/JS tests before the equivalent WPT automation exists. Test: Migrate a WPT to use the state reset binding. Fixed: 1061764 Change-Id: I0d8b9458f89e1ba4c641f27a189480028957094d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2139444 Commit-Queue: David Van Cleve <davidvc@chromium.org> Reviewed-by: Matthew Denton <mpdenton@chromium.org> Reviewed-by: Matt Falkenhagen <falken@chromium.org> Cr-Commit-Position: refs/heads/master@{#759493}
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:
#testing on irc.w3.org; includes participants located around the world, but busiest during the European working day; all discussion is archived hereIf 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.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 http://w3c-test.org/.
Pull requests are automatically mirrored except those that modify sensitive resources (such as .py). The latter require someone with merge access to comment with “LGTM” or “w3c-test:mirror” to indicate the pull request has been checked.
In the vast majority of cases the only upstream branch that you should need to care about is master. If you see other branches in the repository, you can generally safely ignore them.
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!