commit | ee3fd73536dfd44cc1b94df45ef09857a2cdb692 | [log] [tgz] |
---|---|---|
author | Tsuyoshi Horo <horo@chromium.org> | Wed Apr 03 23:38:01 2024 |
committer | Blink WPT Bot <blink-w3c-test-autoroller@chromium.org> | Thu Apr 04 03:45:35 2024 |
tree | 1f710c2efaea02614a1a4118c59643478138dd1a | |
parent | f44b03aa884ff5ddb515ac7bf3aa427290723855 [diff] |
Reland "Add WPT for Compression Dictionary Transport" This reverts commit f27cfea7c57868b51731c9e5d1316f2c952de944. Reason for revert: Relanding dictionary-fetch-with-link-* tests. dictionary-fetch-with-link-* tests are testing the behaviour of fetching a dictionary using link elements or link HTTP header. Fetching a dictionary is internally using requestIdleCallback in blink::PreloadHelper::FetchDictionaryIfNeeded(). But requestIdleCallback doesn't work correctly in the single-threaded compositor mode. So this CL updates VirtualTestSuites for these tests to skip that mode but expect to pass for virtual/threaded. Also this CL make tests wait for a while with requestIdleCallback() to ensure that the dictionary is fetched. Original change's description: > Revert "Add WPT for Compression Dictionary Transport" > > This partially reverts commit f8d14034be021f773bfd4244061f9d3f06915d80. > > Reason for revert: dictionary-fetch-with-link-* tests are flaky. > First failing run > https://ci.chromium.org/ui/p/chromium/builders/ci/Linux%20Tests%20(dbg)(1)/119589/blamelist > > Original change's description: > > Add WPT for Compression Dictionary Transport > > > > Bug: 1413922 > > Change-Id: I4f7aad71a043354f5c107a301b66d58a1409ef89 > > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5401505 > > Commit-Queue: Tsuyoshi Horo <horo@chromium.org> > > Reviewed-by: Patrick Meenan <pmeenan@chromium.org> > > Cr-Commit-Position: refs/heads/main@{#1281548} > > Bug: 1413922 > Change-Id: If52e3f9074e51265da65fef08456fc1d42be735a > No-Presubmit: true > No-Tree-Checks: true > No-Try: true > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5418514 > Reviewed-by: Fergal Daly <fergal@chromium.org> > Commit-Queue: Tsuyoshi Horo <horo@chromium.org> > Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> > Cr-Commit-Position: refs/heads/main@{#1281675} Bug: 1413922 Change-Id: Ie0ac767ff7626c6e2b2811e8631823204a590f8b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5417959 Reviewed-by: Kent Tamura <tkent@chromium.org> Commit-Queue: Tsuyoshi Horo <horo@chromium.org> Reviewed-by: Patrick Meenan <pmeenan@chromium.org> Cr-Commit-Position: refs/heads/main@{#1282208}
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!