commit | da07db4e03aacb060c82996f4ed7b8f0dd4e4b24 | [log] [tgz] |
---|---|---|
author | Liam Brady <lbrady@google.com> | Thu Nov 02 19:32:25 2023 |
committer | Blink WPT Bot <blink-w3c-test-autoroller@chromium.org> | Thu Nov 02 20:41:13 2023 |
tree | 215911fd27ecf2122a41758fe14a87c5547045a0 | |
parent | edffd95f5be7de49876918e25dfcbbb139054711 [diff] |
Introduce reserved.top_navigation_start/commit. Automatic beacons currently have one supported beacon type: reserved.top_navigation. This fires when a navigation commits. There's a need to expand this to support beacons both at navigation start and navigation commit. This CL deprecates reserved.top_navigation in favor of 2 new beacons: reserved.top_navigation_start and reserved.top_navigation_commit. The deprecation is done in order to have a more consistent naming convention. To support multiple automatic beacon types, each beacon type gets its own automatic beacon data. This is stored in a hash map in the fenced frame config, using the event type as the key and the AutomaticBeaconInfo struct as the value. The event type for automatic beacons is now stored as an enumerated type. This makes it simpler to track supported automatic beacon types. This CL refactors automatic beacon tests to support tracking multiple messages. The automatic-beacon-store.py endpoint uses a hash of the message to store a beacon, and then the test passes in the message string to be hashed when checking for the existence of the message. Change-Id: I268f5c75b8ed754cb11e8c176252d124a8270b69 Bug: 1493104 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4953096 Commit-Queue: Liam Brady <lbrady@google.com> Reviewed-by: Avi Drissman <avi@chromium.org> Cr-Commit-Position: refs/heads/main@{#1219027}
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!