web-platform-tests: one suite, every browser engine
Test suites for Web platform specs — including WHATWG, W3C, and others
At a glance
- What is it?
- The wpt repository holds cross-browser tests for WHATWG, W3C and other Web platform specs, arranged one top-level folder per API, driven by a single wpt command, and published through wpt.live and wpt.fyi.
- Who is it for?
- Use this suite when your product depends on a Web API behaving the same way in engines you do not control, and read the results as evidence about engines rather than a certificate about your own code. Before trusting any single run, check which browser build was installed and which manifest the run used, because wpt install always takes the latest release and master is merged continuously.
- Can I use it commercially?
- Check first. The repository uses a licence we do not classify automatically, so read its LICENSE file before any commercial use.
- Is it still maintained?
- Yes. The repository received new commits within the last day.
- What is it written in?
- Mainly HTML, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.
Star history
- web-platform-tests/wpt6,313 ★ · +142
| Repository | 2026-09-23 | 2026-11-15 |
|---|---|---|
| web-platform-tests/wpt | 6.2k | 6.3k |
142 Stars in the last 53 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
One test file, every browser engine
web-platform-tests is a cross-browser test suite for the Web-platform stack. Its premise is plain: a test written so that it can run in all browsers gives browser projects confidence they are shipping software compatible with other implementations, and that later implementations will be compatible with theirs. Web authors and developers get the same confidence in return, because they can rely on the platform working across browsers and devices without extra layers of abstraction papering over the gaps left by specification editors and implementors. The repository holds tests for WHATWG, W3C and other specifications, and its top-level folders follow API areas rather than browsers: FileAPI/, IndexedDB/, WebCryptoAPI/, cookies/, client-hints/, compat/, console/ and compression/ sit beside feature folders such as accelerometer/, ambient-light/, bluetooth/, beacon/, battery-status/ and background-sync/. The primary language of the repository is HTML.
Six wpt subcommands, from serving browsers to manifests
The `wpt` command is a frontend to a variety of tools for working with and running the suite. `wpt serve` starts the project's HTTP server, `wpt run` runs tests in a browser, `wpt lint` runs the lint against all tests, `wpt manifest` updates or generates a `MANIFEST.json` test manifest, `wpt install` installs the latest release of a browser or webdriver server on the local machine, and `wpt serve-wave` starts the HTTP server together with the WAVE test runner. Those six are offered as the most useful of a wider set, so the list is a starting point rather than the whole command surface, and WAVE keeps its own usage notes under tools/wave in the repository. Alongside the test folders sit .azure-pipelines.yml and .taskcluster.yml, plus CODEOWNERS, CODE_OF_CONDUCT.md, CONTRIBUTING.md, .mailmap, .gitattributes, .python-version, .well-known/ and LICENSE.md.
Branch churn: fetch with --prune before you run anything
Setting up the repo means cloning or otherwise getting https://github.com/web-platform-tests/wpt. The project attaches one instruction that most clones would never need, because branches are created and deleted frequently here: prune stale branches when fetching updates, with `git pull --prune` or `git fetch -p && git merge`. How to actually run the tests is documented elsewhere, on the running-tests page of web-platform-tests.org and in particular on its section covering system setup for running tests locally.
git clone https://github.com/web-platform-tests/wpt
cd wpt
git pull --pruneOnce a browser is present, `wpt install` puts the latest release of a browser or a webdriver server on the machine, `wpt serve` starts the HTTP server and `wpt run` runs the tests. Forkers get the same warning from the other direction: if you forked a while ago, stay relatively in sync before you build on top of it.
On Windows, wpt needs python in front and untouched line endings
On Windows every `wpt` command must be prefixed with `python`, or with the path to the python binary when `python` is not in `%PATH%`. The placeholder in the documented form is literal, so `[command]` stands for one of the subcommands above, and a full invocation reads `python wpt serve` on the same machine. The alternative is Bash on Ubuntu on Windows from the Windows 10 Anniversary Update build, launching `wpt` from the Windows partition it exposes. The second Windows-only failure is quieter, because if git or your text editor converts line endings automatically the result is lint errors rather than a missing command, and the fix is one git setting applied in your working tree.
python wpt [command]git config core.autocrlf falsemaster syncs itself to wpt.live and w3c-test.org
Publication needs no ceremony, because the master branch is automatically synced to wpt.live and to w3c-test.org. The last push on the repository is dated 2026-11-01, and the three newest releases are merge_pr_64586, merge_pr_64584 and merge_pr_64583, all published on 2026-11-03. Release names that are merged pull request numbers describe how changes ship: by continuous merge rather than by hand-cut versions. The project also names where its work happens. GitHub is the canonical location for source, revision history and the discussion forum for changes to the code. web-platform-tests.org is the documentation site, covering setup, how to write tests, how to give and receive peer review, and how to serve as an administrator. wpt.live is a public deployment that lets anyone run the tests from an Internet-enabled browser of their choice, and wpt.fyi is an archive of test results collected from an array of browsers on a regular basis. There is a real-time chat room on the `wpt:matrix.org` Matrix channel, busiest during the European working day, a low-traffic public mailing list for test infrastructure, and a separate RFC repository for substantial changes that would impact other stakeholders, which people working on WPT infrastructure are encouraged to watch.
The contribution loop ends at ./wpt lint, not at the editor
The stated position is that absolutely everyone is welcome to contribute test development, and that no test is too small or too simple, especially one that corresponds to an interoperability bug you have noted in a browser. The path itself is short: fork the repository, staying relatively in sync if you forked a while ago, create a branch for your changes, make them, run the lint, commit locally, push that to your fork, and open a pull request based on the above. If you spot an issue with a test and are not comfortable providing the fix yourself, the project asks for a new issue rather than a workaround left in place.
git checkout -b topic
./wpt lintNobody needs permission to add a test, and the lint run is the mechanical gate that sits between an edit and a review.
The AI policy splits test authoring from discussion
Using large language models to help author tests is generally acceptable, with one hard condition attached: every change must be attributable to a human who understands the proposed change and can take responsibility for it. Using them to participate in discussions is generally not acceptable. Any generated content that does appear in a discussion has to come either from a bot account, or be wrapped in a `<blockquote>` element for a short contribution of at most one paragraph, or sit inside a `<details>` element, and the full policy lives on the documentation site under writing-tests. The split falls where it matters: drafting test code can be assisted, while the argument about whether a test belongs in the suite at all stays with the person who signs off on it.
The suite stops at spec conformance, not at your application
Two limits are worth stating plainly. First, the suite measures Web platform specifications, not the code you ship against them. A passing test says an engine implements behaviour that a specification describes in a way other engines also implement, and it says nothing about whether your own application calls that behaviour correctly. The tooling is scoped the same way, since `wpt install` fetches browsers and webdriver servers for the Web platform and for nothing else. Second, the repository README is a map rather than the manual: setup instructions, how to write tests, how to give and receive peer review, and how to serve as an administrator all live on web-platform-tests.org, so the six subcommands above are all that one file tells you about the toolchain. That file also does not document a way to pin a browser release, even though `wpt install` takes the latest one, which leaves run-to-run comparison to whoever reads the archived results at wpt.fyi.
Editorial conclusion
Use this suite when your product depends on a Web API behaving the same way in engines you do not control, and read the results as evidence about engines rather than a certificate about your own code. Before trusting any single run, check which browser build was installed and which manifest the run used, because wpt install always takes the latest release and master is merged continuously.
Frequently asked questions
What is WebTest and what are its features?
That name does not appear in this repository. What lives here is web-platform-tests, a cross-browser suite for the Web-platform stack in which a test written once is run in all browsers, so implementors can check compatibility with other implementations and with later ones.
What is web testing with examples?
Here it means writing tests against Web platform specifications so the same file runs in every browser engine. The suite covers WHATWG, W3C and other specifications, with one top-level folder per API area such as FileAPI/, IndexedDB/ and cookies/. You serve it with wpt serve and run it with wpt run.
What is platform testing?
Platform testing is wider in scope than this repository. web-platform-tests targets one platform, the Web-platform stack, and its tools assume that scope: wpt serve starts the HTTP server, wpt run runs tests in a browser, and wpt install installs the latest release of a browser or webdriver server.
What is the best platform for software testing?
The repository does not weigh software testing platforms against each other. It covers its own corner of the Web platform: cross-browser tests for WHATWG, W3C and other specifications, served publicly at wpt.live, with results collected from an array of browsers on a regular basis archived at wpt.fyi.
Official sources
Add this badge to your README
If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.
[](https://hysenlabs.com/projects/web-platform-tests-wpt)Star history chart for your README
[](https://hysenlabs.com/projects/web-platform-tests-wpt)Was this useful?