gecko-dev/testing/webdriver
Henrik Skupin 421c63d12b Bug 1494617 - [geckodriver] Fix evaluation of "desiredCapabilities" and "requiredCapabilities". r=ato
The refactoring of the webdriver crate to use Serde (bug 1396821)
caused this regression. By instructing Serde to correctly rename
both properties fixes it.

Differential Revision: https://phabricator.services.mozilla.com/D7079

--HG--
extra : moz-landing-system : lando
2018-09-27 12:06:00 +00:00
..
src Bug 1494617 - [geckodriver] Fix evaluation of "desiredCapabilities" and "requiredCapabilities". r=ato 2018-09-27 12:06:00 +00:00
Cargo.toml bug 1490660: webdriver: release 0.37.0; r=jgraham 2018-09-12 16:12:21 +01:00
README.md bug 1490660: webdriver: correct README; r=jgraham 2018-09-12 16:12:20 +01:00
moz.build Bug 1412904 - fill in missing bugzilla_components in testing/webdriver. r=ato 2017-10-31 12:27:48 -04:00

README.md

webdriver library

The webdriver crate is a library implementation of the wire protocol for the W3C WebDriver standard written in Rust. WebDriver is a remote control interface that enables introspection and control of user agents. It provides a platform- and language-neutral wire protocol as a way for out-of-process programs to remotely instruct the behaviour of web browsers.

The webdriver library provides the formal types, error codes, type and bounds checks, and JSON marshaling conventions for correctly parsing and emitting the WebDriver protocol. It also provides an HTTP server where endpoints are mapped to the different WebDriver commands.

As of right now, this is an implementation for the server side of the WebDriver API in Rust, not the client side.

Building

The library is built using the usual Rust conventions:

% cargo build

To run the tests:

% cargo test

Contact

The mailing list for webdriver discussion is tools-marionette@lists.mozilla.org (subscribe, archive).

There is also an IRC channel to talk about using and developing webdriver in #ateam on irc.mozilla.org.