Skip to content
web-platform-tests dashboard
Go JavaScript HTML Python Shell Makefile Other
Branch: master
Clone or download

Latest commit

stephenmcgruer Abstract Taskcluster tasks into their own struct (#1969)
This is a prepatory refactor for the Taskcluster Checks migration.
Instead of using tcqueue.TaskDefinitionAndStatus directly, we extract
the information we actually need into a new taskInfo struct.

The goal is to ultimately share the logic in extractArtifactURLs and
processTaskclusterBuild between the GitHub Status and the (upcoming)
GitHub Checks paths.
Latest commit 6c91b6c May 27, 2020


Type Name Latest commit message Commit time
Failed to load latest commit information.
.github Upgrade to actions/checkout@v2 Feb 28, 2020
.vscode Consolidate the path logic into a shared class (#1346) Jun 13, 2019
ISSUE_TEMPLATE Create issue template for screenshots (#1248) Mar 28, 2019
api Abstract Taskcluster tasks into their own struct (#1969) May 27, 2020
docs Document that /admin/cache/flush does not affect the searchcache Feb 21, 2020
git/hooks Don't repeat rights assurances unless instance is new May 23, 2018
results-processor Scheduled weekly dependency update for week 21 (#1979) May 26, 2020
shared Fix more typos of GitHub May 21, 2020
util Fix version name errors when deploying master May 11, 2020
webapp [webapp] Increase the contrast of "show history" (#1981) May 26, 2020
webdriver Update dependency mocha to v7.2.0 May 23, 2020
.gitignore Cleanup .gitignore and .gcloudignore (#1842) Mar 10, 2020
.pyup.yml Add pyup configuration file Mar 19, 2019
.travis.yml [webapp] Fix lhci upload (#1980) May 26, 2020 Document how to run tests locally (#1115) Feb 5, 2019
Dockerfile Remove mentions of results-collection (#1673) Dec 2, 2019
Makefile Set up Lighthouse CI (#1767) Jan 30, 2020 Tweak the default appearance of the PR template Apr 24, 2018 Add some CI badges (#1916) May 5, 2020
client-secret.json.enc Add Travis staging deploy job (#41) Apr 23, 2018
go.mod Update module to v0.25.0 May 20, 2020
go.sum Update module to v0.25.0 May 20, 2020
renovate.json Fix renovate.json (#1697) Dec 4, 2019

web-platform-tests dashboard 📈

GitHub Actions Travis Status Python Updates 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

Setting up your environment

You'll need Docker. With Docker installed, build the base image and development image, and start a development server instance:

docker build -t wptd-dev .

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:


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

With the webserver running, 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:


See for more information on local development.

Filesystem and network output

  • This script will only write files under config['build_path'].
  • One run will write approximately 111MB to the filesystem.
  • If --upload is specified, it will upload that 111MB of results to GCS.
  • To upload results, you must be logged in with gcloud in the project.

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.

Large-scale analysis

There is no public API for TestRuns, so if you need to access only the most recent results, looking at the main page will give you the latest test SHAs. If you need to access earlier results, an exhaustive search is the only way to do that (see issue #73 and #43).


WPT documentation page for each browser

Location of the WPT in each browser’s source tree

You can run almost any WPT test on

Try out

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



Platform ID

These are the keys in webapp/browsers.json. They're used to identify a tuple (browser name, browser version, os name, os version).

You can’t perform that action at this time.