Repository files navigation

The web-platform-tests Project is a cross-browser test suite for theWeb-platform stack. Writing tests in a way that allows them to be run in allbrowsers gives browser projects confidence that they are shipping software thatis compatible with other implementations, and that later implementations willbe compatible with their implementations. This in turn gives Webauthors/developers confidence that they can actually rely on the Web platformto deliver on the promise of working across browsers and devices withoutneeding extra layers of abstraction to paper over the gaps left byspecification editors and implementors.

The most important sources of information and activity are:

• github.com/web-platform-tests/wpt:the canonical location of the project's source code revision history and thediscussion forum for changes to the code
• web-platform-tests.org: the documentationwebsite; details how to set up the project, how to write tests, how to giveand receive peer review, how to serve as an administrator, and more
• wpt.live: a public deployment of the test suite,allowing anyone to run the tests by visiting from anInternet-enabled browser of their choice
• wpt.fyi: an archive of test results collected from anarray of web browsers on a regular basis
• Real-time chat room: thewpt:matrix.org matrix channel; includes participants locatedaround the world, but busiest during the European working day.
• Mailing list: apublic and low-traffic discussion list
• RFCs: a repo for requestingcomments on substantial changes that would impact other stakeholders orusers; people who work on WPT infra are encouraged to watch the repo.

If you'd like clarification about anything, don't hesitate to ask in thechat room or on the mailing list.

Clone or otherwise gethttps://github.com/web-platform-tests/wpt.

Note: because of the frequent creation and deletion of branches in thisrepo, it is recommended to "prune" stale branches when fetching updates,i.e. usegit pull --prune (orgit fetch -p && git merge).

See thedocumentation websiteand in particular thesystem setup for running tests locally.

Thewpt command provides a frontend to a variety of tools forworking with and running web-platform-tests. Some of the most usefulcommands are:

• wpt serve - For starting the wpt http server
• wpt run - For running tests in a browser
• wpt lint - For running the lint against all tests
• wpt manifest - For updating or generating aMANIFEST.json test manifest
• wpt install - For installing the latest release of a browser orwebdriver 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 thedocumentation.

On Windowswpt commands must be prefixed withpython or the pathto the python binary (ifpython is not in your%PATH%).

python wpt [command]

Alternatively, you may also useBash on Ubuntu on Windowsin the Windows 10 Anniversary Update build, then access your windowspartition from there to launchwpt commands.

Please make sure git and your text editor do not automatically convertline endings, as it will cause lint errors. For git, please setgit config core.autocrlf false in your working tree.

The master branch is automatically synced towpt.live andw3c-test.org.

Save the Web, Write Some Tests!

Absolutely everyone is welcome to contribute to test development. Notest is too small or too simple, especially if it corresponds tosomething for which you've noted an interoperability bug in a browser.

The way to contribute is just as usual:

• Fork this repository (and make sure you're still relatively in syncwith it if you forked a while ago).
• Create a branch for your changes:git checkout -b topic.
• Make your changes.
• Run./wpt lint as described above.
• Commit locally and push that to your repo.
• Create a pull request based on the above.

If you spot an issue with a test and are not comfortable providing apull request per above to fix it, pleasefile a new issue.Thank you!