Test suites for Web platform specs — including WHATWG, W3C, and others

★ 6,315⑂ 4,057👁 399⑃ 60,096● 3,936▤ 47,654
HTMLNOASSERTIONCreated 2012-03-04web-platform-tests.org/
Download: merge_pr_65249merge_pr_65249 ↓652492026-11-15
6,315
stars
4,057
forks
399
watchers
60,096
prs
3,936
issues
47,654
releases

README

The web-platform-tests Project
==============================

   

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:

- github.com/web-platform-tests/wpt:
  the canonical location of the project's source code revision history and the
  discussion forum for changes to the code
- web-platform-tests.org: the documentation
  website; details how to set up the project, how to write tests, how to give
  and 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 an
  Internet-enabled browser of their choice
- wpt.fyi: an archive of test results collected from an
  array of web browsers on a regular basis
- Real-time chat room: the
  wpt:matrix.org matrix channel; includes participants located
  around the world, but busiest during the European working day.
- Mailing list: a
  public and low-traffic discussion list
- RFCs: a repo for requesting
  comments on substantial changes that would impact other stakeholders or
  users; 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 the
chat room or on the mailing list.

Setting Up the Repo
===================

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).

Running the Tests
=================

See the documentation website
and in particular the
system setup for running tests locally.

Command Line Tools
==================

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 server
 wpt run - For running tests in a browser
 wpt lint - For running the lint against all tests
 wpt manifest - For updating or generating a MANIFEST.json test manifest
 wpt 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.

Windows Notes
=================================

Top issues

Latest release

merge_pr_65249 merge_pr_65249 2026-11-15
ci: Use earlyoom to avoid wptrunner being killed

If servo uses too much memory due to a bug, we want servoshell to be
killed, and not python / the wptrunner.

earlyoom helps with that, so we copy the upstream taskcluster
configuration locally and also enable servoshell in the upstream
earlyoom configuration.

Signed-off-by: Jonathan Schwender

Snapshot: 2026-11-16T09:23:14Z · Data license Apache-2.0 · JSON