logo

web-platform-tests/wpt

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

View on GitHub ↗Jump to charts ↓Open shareable report →

web-platform-tests/wpt has 6k+ stars and 3.5k+ forks on GitHub, is written in HTML, and was last pushed on Oct 16, 2026. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 26 minutes ago
Type:Curated List / Learning ResourceCategory(s):Testing, QA & Browser AutomationDeveloper Tools
Added to GitGenius on September 10th, 2026
Created on March 4th, 2012
Open Issues & Pull Requests: 2,918 (-1)
GitHub issues: Enabled
Number of forks: 3,999
Total Stargazers: 6,228 (+0)
Total Subscribers: 403 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 20.1 hours
Mean response time: 117.4 days
90th percentile: 176.0 days
Tracked items: 574

Most active contributors

Sign in to see contributor activity.
Sign in

Related repositories by overlapping contributors

Maintainer activity

23 people did triage or write work on this repository in the last 12 months.

Counts unlabeled, assigned, unassigned, milestoned, demilestoned, locked, unlocked over the last 12 months. These are issue and pull request events that require triage or write permission. Commits and code review are not counted. labeled and renamed are excluded because GitHub issue forms record the issue author as the actor. Figures from October 11, 2026. This count is not comparable across projects: each project's automation decides which of these events a person emits.

How this project is maintained

About 18% of issues opened in the past year have never received a reply. 67% of open issues come from outside the core team, a mix of external reports and the maintainers' own roadmap. Work labelled "wptrunner" is answered fastest, typically in under an hour, while "type:untestable" waits about 8 weeks. 60% of tracked open issues have had no activity in three months, so the open count overstates what is actively being worked. Only 59% of issues opened in the past year have been closed.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 347
New in 7 days: 11
Closed in 7 days: 10
Avg open age: 842 days
Stale 30+ days: 319
Stale 90+ days: 294

Recent activity

Opened in 7 days: 9
Closed in 7 days: 10
Comments in 7 days: 0
Events in 7 days: 11

Top labels

  • infra (220)
  • priority:backlog (149)
  • wptrunner (38)
  • html (29)
  • type:untestable (22)
  • good first issue (21)
  • testharness.js (17)
  • wpt (14)

Most active issues this week

Sign in to see which issues are moving.
Sign in
Explore full issue details

Detailed Description

web-platform-tests is a cross-browser test suite for validating Web platform specification implementations across WHATWG, W3C, and related standards.

The project addresses the need for browsers to verify compatibility with each other and with Web specifications. It provides a unified set of tests that can run across all major browsers, giving browser vendors confidence that their implementations align with standards and with each other. This shared test infrastructure eliminates the need for each browser project to maintain separate test suites and allows Web developers to rely on consistent platform behavior across implementations.

The tool suits anyone involved in browser development, standards implementation, or Web platform testing. Browser vendors use it to validate their implementations against the specification suite. Web developers and standards bodies benefit from the public test results archived at wpt.fyi, which tracks how different browsers perform on the same tests. The project provides multiple entry points: a public deployment at wpt.live allows running tests directly in any browser, while the command-line tools support local development workflows including test serving, linting, manifest generation, and browser automation.

Development activity shows sustained engagement across multiple channels. The project maintains active discussion forums including a real-time chat room with global participation and a low-traffic public mailing list for infrastructure topics. An RFC repository exists for proposing substantial changes that affect stakeholders. The codebase experiences frequent branch creation and deletion, reflecting active development and pull request activity. Documentation is comprehensive and centralized on the project's website, covering setup, test writing, peer review processes, and administrative procedures.