Convert Figma logo to code with AI

web-platform-tests logowpt

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

4,878
3,048
4,878
2,290
View on GitHub

Top Related Projects

web-platform-tests's avatar

wpt

4,878

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

whatwg's avatar

html

7,987

HTML Standard

Quick Overview

The web-platform-tests (WPT) project is a comprehensive test suite for the Web Platform. It contains tests for various web technologies and standards, including HTML, CSS, JavaScript APIs, and more. The project aims to improve interoperability between web browsers by providing a shared set of tests that can be run across different implementations.

Pros

  • Extensive coverage of web standards and APIs
  • Collaborative effort supported by major browser vendors and web developers
  • Helps ensure consistent implementation across different browsers
  • Regularly updated to keep pace with evolving web technologies

Cons

  • Large test suite can be overwhelming for newcomers
  • Running the full test suite can be time-consuming
  • Some tests may be complex or difficult to understand without deep knowledge of web standards
  • Occasional false positives or negatives due to the complexity of web technologies

Getting Started

To get started with web-platform-tests:

  1. Clone the repository:

    git clone https://github.com/web-platform-tests/wpt.git

  2. Install the necessary dependencies:

    cd wpt
./wpt install

  3. Run the tests:

    ./wpt run chrome path/to/test.html

Replace chrome with the browser you want to test (e.g., firefox, safari, etc.) and path/to/test.html with the specific test or directory you want to run.

For more detailed instructions and options, refer to the project's documentation at https://web-platform-tests.org/running-tests/.

Competitor Comparisons

web-platform-tests logo

wpt

4,878

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

Pros of wpt

  • Larger community and more active development
  • More comprehensive test suite covering a wider range of web platform features
  • Better integration with major browser vendors' testing infrastructure

Cons of wpt

  • Potentially more complex setup and maintenance due to its larger scope
  • May include tests for experimental or less widely supported features

Code comparison

wpt:

test(function() {
  assert_true("IntersectionObserver" in window, "IntersectionObserver is supported");
}, "IntersectionObserver is supported");

wpt>:

test(function() {
  assert_true("IntersectionObserver" in window, "IntersectionObserver should be supported");
}, "IntersectionObserver support");

The code comparison shows minor differences in test naming and assertion messages, but the overall structure and purpose remain similar. Both repositories focus on web platform testing, with wpt being the primary and more comprehensive project. The wpt> repository appears to be a fork or alternative version, potentially with some specific modifications or focus areas. However, without more context, it's challenging to determine the exact relationship or differences between the two repositories beyond these surface-level observations.

whatwg logo

html

7,987

HTML Standard

Pros of html

  • Focused specifically on HTML specification, providing a centralized resource for HTML standards
  • Includes detailed explanations and rationales for HTML features and behaviors
  • Allows direct contributions to the HTML specification, influencing web standards

Cons of html

  • Limited scope, focusing only on HTML rather than broader web platform testing
  • Smaller community and fewer contributors compared to the larger wpt project
  • Less frequent updates and slower integration of new web features

Code Comparison

html (HTML specification):

<!DOCTYPE html>
<html lang="en">
<head>
    <meta charset="UTF-8">
    <title>HTML Specification Example</title>
</head>

wpt (Web Platform Tests):

<!DOCTYPE html>
<meta charset="utf-8">
<title>Example Test</title>
<script src="/resources/testharness.js"></script>
<script src="/resources/testharnessreport.js"></script>

The html repository focuses on defining the HTML specification, while wpt provides a comprehensive testing framework for various web platform features. The html codebase primarily consists of the specification document, whereas wpt contains numerous test files covering a wide range of web technologies. wpt's tests are designed to be run across different browsers and platforms to ensure consistent implementation of web standards.

Convert Figma logo designs to code with AI

Visual Copilot

Introducing Visual Copilot: A new AI model to turn Figma designs to high quality code using your components.

Try Visual Copilot

README

The web-platform-tests Project

Taskcluster CI Status documentation manifest Python 3

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

On Windows wpt commands must be prefixed with python or the path to the python binary (if python is not in your %PATH%).

python wpt [command]

Alternatively, you may also use Bash on Ubuntu on Windows in the Windows 10 Anniversary Update build, then access your windows partition from there to launch wpt commands.

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

Publication

The master branch is automatically synced to wpt.live and w3c-test.org.

Contributing

Save the Web, Write Some Tests!

Absolutely everyone is welcome to contribute to test development. No test is too small or too simple, especially if it corresponds to something 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 sync with 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.

Issues with web-platform-tests

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