WebDriver/Marionette/DevNotes

Brief Overview

Marionette will function on the JSON Wire Protocol with support for the remote debugger protocol. It will respond to commands by dispatching the requested actions to the requested targets. This will be done by having Marionette be a root actor that sends our testing requests to an actor that will dispatch the requested action.

Marionette & Eideticker integration

Marionette should support two Eideticker tests:

• start the browser and load a page
• start the browser, do some interaction (click and type), close browser

It should be able to respond to json wire protocol commands that would allow these two tests to complete. Eideticker will no longer need to use JSBridge or its own firefox extension once Marionette has support for these actions.

Initially, we will be allowing an execute script call to come into Marionette. It will execute a blob of Javascript and return the script results Following this, we will allow an execute asynchronous call so that we can support events that require waiting (page load, etc.).

Questions

• How does will the browser work in B2G, how does it behave? Is it the same Fennec or is it different?
• What is the difference between chrome and content in terms of dispatching actions to either group?
• What is the B2G UI environment? XUL, HTML5? How does a11y interface handle them?
• Do we need to worry about a11y in a multiprocess environment (ie: can we dispatch a11y commands to both chrome and content?)