web-platform-tests
Cross-browser test suites for Web platform specifications, ensuring interoperability across browser implementations.
What is web-platform-tests?
web-platform-tests (WPT) is a cross-browser test suite for the Web platform stack, covering specifications from WHATWG, W3C, and other standards bodies. It provides a shared set of tests that browser vendors use to ensure interoperability and compliance, and web developers use to verify feature support across browsers. The project aims to eliminate gaps between specifications and implementations, reducing the need for browser-specific workarounds.
Browser engineers, specification editors, and web developers who need to verify cross-browser compatibility and compliance with Web standards. It's also valuable for QA teams and open-source contributors focused on web platform testing.
Developers choose WPT because it's the de facto standard test suite for the Web platform, maintained collaboratively by browser vendors and the community. Its comprehensive coverage, public deployments (wpt.live, wpt.fyi), and tooling make it indispensable for ensuring interoperability and tracking browser implementation progress.
Overview
Test suites for Web platform specs — including WHATWG, W3C, and others
Use Cases
Best For
- Browser vendors verifying specification compliance and interoperability
- Web developers testing cross-browser compatibility of new features
- Standards bodies validating specification implementations
- QA engineers automating web platform testing
- Open-source contributors writing tests for web standards
- Researchers studying web platform interoperability and browser behavior
Not Ideal For
- Teams developing non-web applications like native mobile or desktop apps
- Projects needing simple unit tests for custom JavaScript without browser automation
- Organizations with limited resources for maintaining Python and complex git workflows
- Developers seeking a GUI-based test runner or integrated development environment
Pros & Cons
Pros
Enables running the same tests across all major browsers to detect interoperability gaps, as emphasized in the README's philosophy of reducing abstraction layers.
Tests align with WHATWG and W3C specifications, validating standard compliance and providing confidence in web platform reliability.
Offers wpt.live for direct browser testing and wpt.fyi for archived results, making it accessible without local setup, as highlighted in the key features.
Provides a `wpt` CLI for serving tests, running locally, linting, and managing browser/webdriver installations, streamlining workflows as described in the README.
Cons
Requires specific system setup, Python installation, and on Windows, additional steps like prefixing commands with `python` or using Bash, as noted in the README's Windows notes.
Information is spread across multiple sites (GitHub, web-platform-tests.org, wpt.live, etc.), which can confuse new users and hinder troubleshooting.
Contributing involves understanding web standards, running lint, managing git branches with pruning, and following RFC processes, which may deter casual contributors.
Exclusively targets web platform specifications, making it unsuitable for testing custom or non-standard features, limiting its use for general application testing.
Frequently Asked Questions
Found a gem we're missing?
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.