| commit | 9cc314e8042e9637b1eeb1836e462b19fe7730d3 | [log] [tgz] |
|---|---|---|
| author | jgraham <james@hoppipolla.co.uk> | Tue Aug 22 16:59:17 2023 |
| committer | GitHub <noreply@github.com> | Tue Aug 22 16:59:17 2023 |
| tree | aa2ae5bef5da63e73b9e5fff9e8380fdff92c287 | |
| parent | 3c44fc63c0bd7b1a4a1ae4b6d7d8889f8bf557ba [diff] |
Add subsuite support to wptrunner (#39711)
* Add support for subsuites in wptrunner
Subsuites are alternate test configurations that are able to run as
part of a single test run (e.g. so that they can be run in parallel).
The mechanism for defining a subsuite is to provide the path to a json
file as the `--subsuite-file` command line argument. This has the
following structure:
{
<subsuite_name>: {
config: <object>,
run_info: <object>,
include: [<string>],
tags: [<string>]
}
}
All the per-subsuite fields are optional.
"config" defines the configuration of the subsuite. This is
interpreted by individual products, when deciding the browser_kwargs and
executor_kwargs for test groups in the subsuite.
"run_info" is additional configuration information for the
subsuite. This provides extra information that can be used for the
subsuite in metadata files. The subsuite name is automatically added
as a `subsuite` key in the metadata.
"include" is a list of test URL prefixes to include in the subsuite.
"tags" is a list of metadata tags for tests to include in the
subsuite.
Conceptually the implementation replaces all the objects that were
previously keyed on test_type by (subsuite, test_type). This means we
get different Browser and Executor instances for each subsuite. This
implementation means that we have to restart the browser between
subsuites even if that might theoretically be unnecessary (e.g. just
setting different prefs which can be changed at runtime). However
since this meets all of the known requirements, and it's simpler than
a design which allows multiple subsuites in the same browser/executor
instance, it seems like a reasonable tradeoff.
Differential Revision: https://phabricator.services.mozilla.com/D172000
* Add support for subsuites to firefox
This allows subsuites to depend on prefs or command line arguments
Differential Revision: https://phabricator.services.mozilla.com/D172001
* Add subsuite support to wptreport formatter
This adds a top-level key listing all subsuites defined in the current
suite, and their run_info updates, and gives each test result a
subsuite key naming the subsuite it belongs to.
Differential Revision: https://phabricator.services.mozilla.com/D172002
* Add support for subsuites in wpt-update
This just requires looking up the correct run_info per subsuite rather than assuming
a 1:1 relationship between subsuites and run_info data
Differential Revision: https://phabricator.services.mozilla.com/D172003
Co-authored-by: Weizhong Xia <weizhong@google.com>
Co-authored-by: Weizhong Xia <77710146+WeizhongX@users.noreply.github.com>
Co-authored-by: Jonathan Lee <jonathan-j-lee@users.noreply.github.com>
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:
wpt:matrix.org matrix channel; includes participants located around the world, but busiest during the European working day.If you'd like clarification about anything, don't hesitate to ask in the chat room or on the mailing list.
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).
See the documentation website and in particular the system setup for running tests locally.
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 serverwpt run - For running tests in a browserwpt lint - For running the lint against all testswpt manifest - For updating or generating a MANIFEST.json test manifestwpt 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.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.
The master branch is automatically synced to wpt.live and w3c-test.org.
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:
git checkout -b topic../wpt lint as described above.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!