| commit | 2ee22c6ca2b596c34af3d316a0bcf7dd68f9799b | [log] [tgz] |
|---|---|---|
| author | Youssef Bourouphael <ybourouphael@google.com> | Mon May 06 21:10:39 2024 |
| committer | Blink WPT Bot <blink-w3c-test-autoroller@chromium.org> | Tue May 07 02:08:12 2024 |
| tree | 5ee2290bff41769c7513a7e91e49cb06ffaf7576 | |
| parent | 3e4c9ae2ccb08eab382ca495d2d02e1a9458049f [diff] |
Revert "Reland "Service worker web platform tests."" This reverts commit 436f1b9f6153002fd41599d5d4ec8343cf930a43. Reason for revert: There are still timeouts in some tests Original change's description: > Reland "Service worker web platform tests." > > This reverts commit 36a1c457dac0ecaa54c0553b28f67c0c61752494. > > Reason for revert: The test that looks for 'update-url.py' takes too long and therefore will require this test file to be part of slowTests > > Original change's description: > > Revert "Service worker web platform tests." > > > > This reverts commit 63858f1b1ed058d07e73cebb0a98214aa2cfc715. > > > > Reason for revert: New test added; fails immediately on some bots. > > > > See > > https://ci.chromium.org/ui/p/chromium/builders/ci/mac11-arm64-rel-tests/38089/overview > > for the first failures. (And consistently in subsequent builds) > > > > Original change's description: > > > Service worker web platform tests. > > > > > > This tests that when an auction is ran, service workers do not intercept requests with URLs that are meant to be private. > > > > > > > > > Bug: 293383734 > > > Change-Id: I06858f7cae4794a35c045fb8dad30d6316a26ead > > > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5459094 > > > Commit-Queue: Youssef Bourouphael <ybourouphael@google.com> > > > Reviewed-by: mmenke <mmenke@chromium.org> > > > Reviewed-by: Orr Bernstein <orrb@google.com> > > > Cr-Commit-Position: refs/heads/main@{#1294960} > > > > Bug: 293383734 > > Change-Id: I3431f0e45e65767ff1529002d8a2d14657d0cb5a > > No-Presubmit: true > > No-Tree-Checks: true > > No-Try: true > > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5506634 > > Auto-Submit: Ian Clelland <iclelland@chromium.org> > > Owners-Override: Ian Clelland <iclelland@chromium.org> > > Commit-Queue: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> > > Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> > > Cr-Commit-Position: refs/heads/main@{#1295015} > > Bug: 293383734 > Change-Id: I762dd50282f99617796df64d73a27d149cac0a86 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5512083 > Commit-Queue: Youssef Bourouphael <ybourouphael@google.com> > Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> > Reviewed-by: Orr Bernstein <orrb@google.com> > Reviewed-by: mmenke <mmenke@chromium.org> > Cr-Commit-Position: refs/heads/main@{#1296948} Bug: 293383734 Change-Id: I9b06c0453656aaa448d0030960a48fc264bcf867 No-Presubmit: true No-Tree-Checks: true No-Try: true Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5515623 Auto-Submit: Youssef Bourouphael <ybourouphael@google.com> Commit-Queue: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> Commit-Queue: mmenke <mmenke@chromium.org> Reviewed-by: mmenke <mmenke@chromium.org> Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> Cr-Commit-Position: refs/heads/main@{#1297048}
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!