commit | a38612f39e7752c3532080c7b482e3c8627f7f76 | [log] [tgz] |
---|---|---|
author | jgraham <james@hoppipolla.co.uk> | Wed Jun 23 10:48:06 2021 |
committer | GitHub <noreply@github.com> | Wed Jun 23 10:48:06 2021 |
tree | 5702bf20722e2e396600f5d69b5435a4305e7d2d | |
parent | 545f8a52dc7569cce70394bd2b59d527fd32faf6 [diff] |
Start creating a proper client for WebDriver BiDi (#28381) Add a webdriver.bidi.client module with a BidiSession class that implements only the BiDi part of the protocol. An ordinary Session may have an associated BidiSession if the session was created through HTTP. To make this easier, an enable_bidi flag is added to the top-level session which automatically sets the capabilities required to enable BiDi. The session allows sending commands, and registering handlers for events. In addition to the session class, this adds some intial work on creating a structure for commands, with a BidiModule abstract class that can be used as the basis for command implementations and an @command decorator that handles actually sending the command and waiting for the result. Co-authored-by: Maksim Sadym <69349599+sadym-chromium@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:
#testing
on irc.w3.org; includes participants located around the world, but busiest during the European working day; all discussion is archived hereIf 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.
Pull requests are automatically mirrored except those that modify sensitive resources (such as .py
). The latter require someone with merge access to comment with “LGTM” or “w3c-test:mirror” to indicate the pull request has been checked.
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!