WebDriver/Marionette: Difference between revisions

Line 16: Line 16:
== Design and Implementation ==
== Design and Implementation ==


The current design grew from the ideas presented [[Auto-tools/Projects/JSON Protocol Testing|here]]. We selected [https://wiki.mozilla.org/Auto-tools/Projects/JSON_Protocol_Testing#Approach_3:_.22Surgical_Strike.22_aka_The_Debugger_Approach approach#3].
Note: The current design grew from the ideas presented [[Auto-tools/Projects/JSON Protocol Testing|here]]. We selected [https://wiki.mozilla.org/Auto-tools/Projects/JSON_Protocol_Testing#Approach_3:_.22Surgical_Strike.22_aka_The_Debugger_Approach approach#3].


The [https://wiki.mozilla.org/Platform/JSDebugv2 remote-debugger] is a means of sending remote debugging commands over a socket connection. We can integrate our command dispatcher to the remote-debugger in the form of an [https://wiki.mozilla.org/Remote_Debugging_Protocol#Actors Actor]. This will allow us to connect to the socket and send debug commands to the remote-debugger specific actors, or send our testing commands to our testing actor.
In order to send the JSON commands to the mobile device, we will use the already written socket listener/debugger, [https://wiki.mozilla.org/Platform/JSDebugv2 remote-debugger]. We can integrate our command dispatcher to the remote-debugger in the form of an [https://wiki.mozilla.org/Remote_Debugging_Protocol#Actors Actor]. This will allow us to connect to the socket and send debug or testing commands by addressing the JSON messages to the appropriate actor.


Once the testing actor receives the testing command, it will dispatch it to the appropriate test harness or listener. For now, we plan to use the [https://developer.mozilla.org/en/nsIAccessible accessibility (a11y) interfaces] that is already supported by the platform. For actions not covered by a11y, like gestures, we should be able to fire off events directly to the mobile device's event queue.
Once the testing actor receives the testing command, it will dispatch it to the appropriate test harness or listener. For now, we plan to use the [https://developer.mozilla.org/en/nsIAccessible accessibility (a11y) interfaces] that is already supported by the platform. For actions not covered by a11y, like gestures, we should be able to fire off events directly to the mobile device's event queue.
Confirmed users
561

edits