Confirmed users
561
edits
WebDriver/Marionette: Difference between revisions
Jump to navigation
Jump to search
→Design and Implementation
| Line 18: | Line 18: | ||
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]. | 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]. | ||
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. | 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. The remote-debugger code is subject to change as it is not yet part of mozilla-central, so the design may change if anything radical happens. | ||
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. | ||