如果你没有耐心看完，请记住下面几个重点：

Mobile JSON Wire Protocol Specification 这个标题就不翻译了

源地址

DRAFT草稿 (注意，这是草稿，也就是说会变的)

Introduction 简介

下面这段的大意是以前的 JsonWireProtocol 现在需要进行扩展了。因为要支持移动化了。

This specification is designed to extend the JSON Wire
Protocol (JSONWP),
a W3C working draft for web browser automation. The JSONWP has been greatly
successful for that purpose. The need for automation of native and hybrid
mobile applications can be met by the extension of the JSONWP, which already
has a proven basic automation framework (architecture, interaction model,
etc...).

最初的版本是由下面一群牛人在 Mozilla 的办公室里捣鼓出来的。

The initial details of this specification were worked out at a series of
meetings held in Mozilla's offices in London in August of 2013. The
participants were:

Sessions 会话

跟 webdriver 一样，POST /session 这个 URI，然后 server 给你返回一个 sessionId。
然后通过这个 sessionId，你可以得寸进尺，为所欲为。

如果 server 没办法 start session，那么返回的状态码是 500。

Session 通过 DELETE /session/:id 这个 URI 进行销毁，跟 webdriver 一样。

下面一段是关于 AUT 的，有兴趣自研。

Sessions work just like WebDriver: you POST to /session and receive a sessionId
as a response if the server can give you one, at which point you can send
further automation commands. If the server can't start a session, for example
if another session is running and only one session can be handled at a time,
the server must return the appropriate 500 response. Sessions are ended with
a DELETE to /session/:id as per the original WebDriver spec.

The server may but is not required to launch the AUT or a device/simulator in
the process of creating a session. It may but is not required to perform some
kind of cleaning or resetting of the AUT in order to provide a clean test
environment. It may but is not required to stop the running AUT at the session
end. It may but is not required to remove the AUT from the device or otherwise
reset the device state after the session is complete. In general, it is the
responsibility of the user to manage the test environment; it is not a part of
this specification. But a server conforming to this specification may by other
means provide that functionality as a convenience.

Desired Capabilities 不知道怎么翻，反正就是做配置的

有一些新的 key 了

New desired capability keys:

Locator Strategies 新的定位策略，重点

非 HTML 平台，下面的这些策略是需要支持的。

The following locator strategies must be supported for non-HTML-based platforms:

下面这些是可选的，也就是说想支持就支持，不想就算了

The following locator strategies may be supported, depending on the automation
platform:

如果是用 webdriver 的模式或者是使用了 HTML 的平台，那么需要支持 webdriver 的定位策略。不罗嗦。

If automating a mobile browser in WebDriver mode, or a platform that uses HTML
as its element hierarchy, the usual array of WebDriver commands must be
supported instead, with their usual semantics.

Page Source 页面源码，真牵强

所有的平台必须支持 GET source 命令。返回代表其 UI 层级的 xml(html)。

其他的不翻了。

All platforms must respond to the GET source command with an XML (or HTML in
the case of HTML-based platforms) document representing the UI hierarchy. The
precise structure of the document may differ from platform to platform. Schemas
that must be followed for iOS and Android automation are as follows:

TODO: get together schemas for UIAutomation (iOS), Instruments (Android), and
UiAutomator (Android).

The elements in these documents may be augmented with such attributes as, for
example, ids, in order to support internal behaviors.

Touch Gestures 触摸手势

所有平台都要支持 Mozila 提出的 Multi-Action API（这个谁能告诉我怎么翻），在一些情况下如果无法支持，直接返回 500.

All platforms must adopt the Multi-Action API pioneered by Mozilla. In some
cases it will not be possible to support the full range of gestures potentially
described by this API on a given platform. In this case, the platform should
respond with a 500 when it cannot faithfully render the requested gesture.

TODO: show what the gestures API actually looks like in terms of server
endpoints that must be supported.

Device Modes 设备模式

设备有很多的网络连接状态，为了能够精准控制，我们提供了下面的 endpoints。

Remote 端必须相应"networkConnectionEnabled"这个 capability。

其他的自己看。

Devices have various states of network connectivity. In order to control
those states we have the following endpoints:

Setting the network connection in the POST returns the ConnectionType because
the device might not be capable of the network connection type requested.

The remote end MUST reply with the capability "networkConnectionEnabled"

ConnectionType - 连接类型

这里是指定了具体的值，可以不用理解。

Value (Alias) | Data | Wifi | Airplane Mode

1 (Airplane Mode) | 0 | 0 | 1
6 (All network on) | 1 | 1 | 0
4 (Data only) | 1 | 0 | 0
2 (Wifi only) | 0 | 1 | 0
0 (None) | 0 | 0 | 0

如果是飞行模式，那么就返回:

{ "name": "network_connection", "parameters": { "type": 1 } }

以后将支持更多的类型，比如 3G，4G，LTE。

Is a bit mask that should be translated to an integer value when serialized.

Value (Alias) | Data | Wifi | Airplane Mode

1 (Airplane Mode) | 0 | 0 | 1
6 (All network on) | 1 | 1 | 0
4 (Data only) | 1 | 0 | 0
2 (Wifi only) | 0 | 1 | 0
0 (None) | 0 | 0 | 0

Example payload for setting "Airplane Mode":

{ "name": "network_connection", "parameters": { "type": 1 } }

Data is the upper bits since in the future we may want to support setting
certain types of Data the device is capable of. For example 3G, 4G, LTE.

Other Device Features

Mobile devices have a variety of sensors and input methods. These are automated
as follows:

WebViews and Other Contexts

One common feature of mobile platforms is the ability to embed a chromeless
webbrowser inside of a 'native' application. These are called 'webviews', and,
if possible, a server for a given platform should implement support for
automating the webview using the full, regular, WebDriver API.

This creates a situation where there are two potential contexts for automation
in a given AUT: the native layer and the webview layer. If providing webview
support, the server must have the following endpoints:

The first endpoint must return a possibly-empty array of strings. Each string
must be the arbitrary name of an available context, e.g., one of possibly
multiple webviews. The second must interpret the body of the request as the
name of an available context. If that context is not found, a NoSuchContext
error must be returned. If the context is available, the server must switch
automation to that context, such that all subsequent commands are taken to
apply to that context. If the body of the POST is null, the server must
return to the original context.

If a server receives a request at an endpoint which is valid in some context
but not the currently active context (for example if a user calls
driver.get() in a native context instead of a webview context), the server
must respond with an InvalidContentException.

Waiting for Conditions

The server must respond to the management commands for implicit wait timeouts,
such that when a user sets an implicit wait timeout and tries to find an
element(s), the server keeps trying to find the element(s) until that timeout
expires, rather than responding with the first failure to find the element(s).

TODO: figure out what the serversidewait implementation will be and talk about
it.
Hide details
Change log
2a302804fc1d by Luke Inman-Semerau linman-s...@salesforce.com on May 5, 2014 Diff
using "network_connectivity" enpoint
instead of toggling just airplane mode

passing a 'bitmask' for the types of
network connectivity desired
Go to:

Double click a line to add a comment
Older revisions
7a8d40f61557 by Jonathan Lipps on Apr 2, 2014 Diff
ba61c96e26c8 by Jonathan Lipps on Mar 27, 2014 Diff
5432d87357e0 by Jonathan Lipps on Feb 25, 2014 Diff
All revisions of this file
File info
Size: 9179 bytes, 198 lines
View raw file


↙↙↙阅读原文可查看相关链接，并与作者交流