gecko-dev/testing/webdriver
Bastien Orivel b5e0d251ee Bug 1562043 - Fix a debug statement when processing webdriver requests. r=ato
Since we moved to warp, this debug statement was printing the
unprocessed path (i.e `/session/{sessionId}`) because the closure didn't
know about the real path that was called (it only knew about the route
that was triggered and the parameters that were passed).

I added a warp filter to get the unprocessed full path to be able to
make logging useful again. This also fixes the body which had an extra
Result around it when it was debugged.

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

--HG--
extra : moz-landing-system : lando
2019-07-08 09:54:25 +00:00
..
src Bug 1562043 - Fix a debug statement when processing webdriver requests. r=ato 2019-07-08 09:54:25 +00:00
Cargo.toml Bug 1396824 - Part 1: Replace the webdriver router by warp. r=ato 2019-06-24 09:26:59 +00:00
moz.build
README.md Bug 1520137: Update documentation pointing to #interop instead of #ateam r=whimboo 2019-01-15 14:14:10 +00:00

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.