commit | 9e04c1f62688fb667fe1b27297b77f9ffe29cc86 | [log] [tgz] |
---|---|---|
author | Mason Freed <masonf@chromium.org> | Sat Sep 10 08:11:07 2022 |
committer | Blink WPT Bot <blink-w3c-test-autoroller@chromium.org> | Sat Sep 10 08:32:00 2022 |
tree | 42ceed32471d172b47fc47fa17919f86c9fd9705 | |
parent | 1fc9ba6302ecfadf79866e7c9c28603d6e7c872a [diff] |
Move Anchor Positioning WPTs from wpt-internal to WPT proper There are some folks working on polyfills for this feature, and they'd like to use the public WPTs to test against. Because these are in the internal folder, they're not published to WPT.fyi. This CL moves them into external/wpt/css, and renames them to .tentative, which should have the same effect as being in wpt-internal (in terms of browsers testing against them), yet will make them more easily accessible. E.g. the external folks won't need to do something special to pull them out of Chromium's repo, but can instead just use them as they use other WPTs. This is a mostly-mechanical move, with a few small exceptions. The move to WPT required me to add explicit links to the Ahem font, and also to rename `images` to `support`. These should not make any functional difference. Bug: 1309178 Change-Id: Iaba3b86fc2e34351d07f90096427c4d2a71cfadd Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3887743 Commit-Queue: Koji Ishii <kojii@chromium.org> Auto-Submit: Mason Freed <masonf@chromium.org> Reviewed-by: Koji Ishii <kojii@chromium.org> Cr-Commit-Position: refs/heads/main@{#1045499}
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!