b5e0d251ee
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
|
||
|---|---|---|
| .. | ||
| 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.