commit | fe3c6d583713c0da55254088217bb823c8e2c9d5 | [log] [tgz] |
---|---|---|
author | James Graham <james@hoppipolla.co.uk> | Wed Apr 06 09:59:29 2022 |
committer | jgraham <james@hoppipolla.co.uk> | Wed Apr 06 19:15:56 2022 |
tree | 5a974767535ffbd7bc7d60d473f622ba8a2eb81f | |
parent | 53f13b1dbadec927bc62385451068bcc0293042e [diff] |
Re-add __init__.py files where Python handlers do relative imports This partially reverts commit 3586ff740b00aa1fa82ab00cccbc36cca0bb8ccb. We previously believed that PEP 420 meant that we didn't need __init__.py files in each directory to allow relative imports. But it turns out this isn't really the case; PEP 420 allows the creation of "namespace packages" which are single packages split over multiple directories. But per https://bugzilla.mozilla.org/show_bug.cgi?id=1760301 we weren't (as we perhaps thought) successfully turning the entirety of wpt into a single namespaced package. I'm still somewhat confused about the whole situation and don't really know why this works in some cases (gecko CI) but not others (gecko locally), but in any case reverting the __init__.py removal seems like the right way forward.
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!