f3071e8691
webdriver depends on the regex crate for unit testing which adds significant overhead building the crate. We could depend on serde_json::from_value() instead, following the same pattern set forth in the marionette crate. Differential Revision: https://phabricator.services.mozilla.com/D48318 --HG-- extra : moz-landing-system : lando |
||
|---|---|---|
| .. | ||
| src | ||
| Cargo.toml | ||
| README.md | ||
| moz.build | ||
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 #interop on irc.mozilla.org.