Skip to content

Latest commit

 

History

History
74 lines (44 loc) · 3.26 KB

README.md

File metadata and controls

74 lines (44 loc) · 3.26 KB

GitHub Actions

wpt.fyi is a dashboard of cross-browser results for web-platform-tests, the data for which is uploaded by external services, primarily from various CI integrations in the wpt repo.

Backend: An App Engine app for storing test run metadata and serving HTML

Frontend: Polymer elements for loading and visualizing test results

Using the data

All test result data is public. Please use our APIs to explore the data. For example, use the results API to download result summaries, and use the runs API to query runs and their metadata, which include links to other data like raw full reports.

Product ID

This is a tuple of browser name, browser version, os name, os version, serialized in the form of browser[-version[-os[-version]]] ([] means optional), widely used in our APIs as the product parameter.

Development

Setting up your environment

You'll need Docker. With Docker installed, start the development container:

docker pull webplatformtests/wpt.fyi:latest   # Optional: this forces fetching the latest version, instead of using the locally cached version.
./util/docker-dev/run.sh

This starts a Docker instance named wptd-dev-instance.

Running locally

Once the instance is running, you can fire up the web server in another terminal:

./util/docker-dev/web_server.sh

This will build dependencies and start the Google App Engine development server inside wptd-dev-instance.

Meanwhile, you'll also need to populate the app datastore with some initial data. In another terminal, execute the script which leverages util/populate_dev_data.go by running:

./util/docker-dev/dev_data.sh

See CONTRIBUTING.md for more information on local development.

Miscellaneous

WPT documentation page for each browser

Location of the WPT in each browser’s source tree

You can run almost any WPT test on wpt.live

Try out http://wpt.live/html/semantics/forms/the-input-element/checkbox.html

This doesn't work with some HTTPS tests. Also be advised that the server is not intended for frequent large-scale test runs.

Sources of inspiration