#webdriver #browser #automation #protocol #w3c


Library implementing the wire protocol for the W3C WebDriver specification

55 releases (breaking)

0.40.2 Sep 9, 2019
0.39.0 Jan 28, 2019
0.38.0 Oct 4, 2018
0.36.0 Jun 15, 2018
0.2.2 Jul 22, 2015

#58 in Testing

Download history 795/week @ 2019-09-26 794/week @ 2019-10-03 550/week @ 2019-10-10 968/week @ 2019-10-17 806/week @ 2019-10-24 753/week @ 2019-10-31 752/week @ 2019-11-07 1063/week @ 2019-11-14 1026/week @ 2019-11-21 791/week @ 2019-11-28 1175/week @ 2019-12-05 1180/week @ 2019-12-12 534/week @ 2019-12-19 268/week @ 2019-12-26 969/week @ 2020-01-02

3,727 downloads per month
Used in 7 crates (6 directly)

MPL-2.0 license

4.5K SLoC

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.


The library is built using the usual Rust conventions:

% cargo build

To run the tests:

% cargo test


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.


~241K SLoC