Interoperability between browsers is critical to Chromium's mission of improving the web. We believe that leveraging and contributing to a shared test suite is one of the most important tools in achieving interoperability between browsers. The web-platform-tests repository is the primary shared test suite where all browser engines are collaborating.
Chromium has a 2-way import/export process with the upstream web-platform-tests repository, where tests are imported into LayoutTests/external/wpt and any changes to the imported tests are also exported to web-platform-tests.
See http://web-platform-tests.org/ for general documentation on web-platform-tests, including tips for writing and reviewing tests.
Chromium has a mirror of the GitHub repo and periodically imports a subset of the tests to run as part of the regular Blink layout test testing process.
The goals of this process are to be able to run web-platform-tests unmodified locally just as easily as we can run the Blink tests, and ensure that we are tracking tip-of-tree in the web-platform-tests repository as closely as possible, and running as many of the tests as possible.
There is an automatic process for updating the Chromium copy of web-platform-tests. The import is done by the builder wpt-importer builder.
The easiest way to check the status of recent imports is to look at:
The import jobs will generally be green if either there was nothing to do, or a CL was successfully submitted.
If the importer starts misbehaving, it could be disabled by turning off the auto-import mode by landing this CL.
If there are new test failures that start after an auto-import, there are several possible causes, including:
Because these tests are imported from the Web Platform tests, it is better to have them in the repository (and marked failing) than not, so prefer to add test expectations rather than reverting. However, if a huge number of tests are failing, please revert the CL so we can fix it manually.
If you upload a CL with any changes in third_party/WebKit/LayoutTests/external/wpt, once you add reviewers the exporter will create a provisional pull request with those changes in the upstream WPT GitHub repository.
Once you‘re ready to land your CL, please check the Travis CI status on the upstream PR (link at the bottom of the page). If it’s green, go ahead and land your CL and the exporter will automatically remove the “do not merge yet” label and merge the PR.
If Travis CI is red on the upstream PR, please try to resolve the failures before merging. If you run into Travis CI issues, or if you have a CL with WPT changes that the exporter did not pick up, please reach out to ecosystem-infra@chromium.org.
Additional things to note:
chromium-export label.do not merge yet label.For maintainers:
We control which tests are imported via a file called W3CImportExpectations, which has a list of directories to skip while importing.
In addition to the directories and tests explicitly skipped there, tests may also be skipped for a couple other reasons, e.g. if the file path is too long for Windows. To check what files are skipped in import, check the recent logs for wpt-importer builder.
When manually running the wpt-import and wpt-export scripts, several requests are made to GitHub to query the status of pull requests, look for existing exported commits etc. GitHub has a fairly low request limit for unauthenticated requests, so it is recommended that you let wpt-export and wpt-import use your GitHub credentials when sending requests:
GH_USER environment variable to your GitHub user name and the GH_TOKEN environment variable to the access token you have just created orGH_USER, your GitHub user name, and GH_TOKEN, the access token you have just generated. After that, pass --credentials-json <path-to-json> to wpt-export and wpt-import.To pull the latest versions of the tests that are currently being imported, you can also directly invoke the wpt-import script.
That script will pull the latest version of the tests from our mirrors of the upstream repositories. If any new versions of tests are found, they will be committed locally to your local repository. You may then upload the changes.
Remember your import might fail due to GitHub's limit for unauthenticated requests, so consider passing your GitHub credentials to the script.
If you wish to add more tests (by un-skipping some of the directories currently skipped in W3CImportExpectations), you can modify that file locally and commit it, and on the next auto-import, the new tests should be imported.
If you want to import immediately (in order to try the tests out locally, etc) you can also run wpt-import, but this is not required.
Remember your import might fail due to GitHub's limit for unauthenticated requests, so consider passing your GitHub credentials to the script.
To contribute changes to web-platform-tests, just commit your changes directly to LayoutTests/external/wpt and the changes will be automatically upstreamed within 24 hours.
Changes involving adding, removing or modifying tests can all be upstreamed. Any changes outside of external/wpt will not be upstreamed, and any changes *-expected.txt, OWNERS, and MANIFEST.json, will also not be upstreamed.
Running the layout tests will automatically regenerate MANIFEST.json to pick up any local modifications.
Most tests are written using testharness.js, see Writing Layout Tests and Layout Tests Tips for general guidelines.
Tests in web-platform-tests are expected to match behavior defined by the relevant specification. In other words, all assertions that a test makes should be derived from a specification‘s normative requirements, and not go beyond them. It is often necessary to change the specification to clarify what is and isn’t required.
When implementation experience is needed to inform the specification work, tentative tests can be appropriate. It should be apparent in context why the test is tentative and what needs to be resolved to make it non-tentative.
testdriver.js provides a means to automate tests that cannot be written purely using web platform APIs, similar to internals.* and eventSender.* in regular Blink layout tests.
If no testdriver.js API exists, check if it's a known issue and otherwise consider filing a new issue.
An alternative is to write manual tests that are automated with scripts from wpt_automation. Injection of JS in manual tests is determined by loadAutomationScript in testharnessreport.js.
Such tests still require case-by-case automation to run for other browser engines, but are more valuable than purely manual tests.
Manual tests that have no automation are still imported, but skipped in NeverFixTests; see issue 738489.
Entirely new top-level directories should generally be added upstream, since that's the only way to add an OWNERS file upstream. After adding a new top-level directory upstream, you should add a line for it in W3CImportExpectations.
Adding the new directory (and W3CImportExpectations entry) in Chromium and later adding an OWNERS file upstream also works.
The email you commit with in Chromium will be the author of the commit on GitHub. You can add it as a secondary address on your GitHub account to link your exported commits to your GitHub profile.
If you are a Googler, you can also register your GitHub account at go/github, making it easier for other Googlers to find you.
This cannot be avoided entirely as the two repositories are independent, but should be rare with frequent imports and exports. When it does happen, manual intervention will be needed and in non-trivial cases you may be asked to help resolve the conflict.
It's still possible to make direct pull requests to web-platform-tests, see http://web-platform-tests.org/appendix/github-intro.html.
Same as Blink layout tests, you can use run-webkit-tests to run any WPT test.
One thing to note is that glob patterns for WPT tests are not yet supported.
Anyone who can review code and tests in Chromium can also review changes in external/wpt that will be automatically upstreamed. There will be no additional review in web-platform-tests as part of the export process.
If upstream reviewers have feedback on the changes, discuss on the pull request created during export, and if necessary work on a new pull request to iterate until everyone is satisfied.
When reviewing tests, check that they match the relevant specification, which may not fully match the implementation. See also Write tests against specifications.