Appium-Automating hybrid apps(自动化混合应用程序)

港控/mmm° 2023-01-19 10:54 20阅读 0赞

### Automating hybrid apps ###

*   *   *   *   *  Entering the web view context
                 *  Automatically entering the web view context on session start
                 *  Examples
                 *  Automating hybrid Android apps
                 *  Automating hybrid iOS apps
                 *  Execution against an iOS real device

One of the core principles of Appium is that you shouldn’t have to change your app to test it. In line with that methodology, it is possible to test hybrid apps the same way you can with Selenium for web apps. There is a bit of technical complexity required so that Appium knows whether you want to automate the native aspects of the app or the web views. But, thankfully, we can stay within the Selenium WebDriver protocol for everything.

Appium一个核心准则是你不应该为了测试它去改变你的应用程序.
    按照这个原则，
    你可以使用Selenium for web apps以同样的方式去测试混合应用程序.
    有些关于技术复杂性要求以便Appium知道你是否想自动化应用程序或web views.
    但是，幸运的是，
    我们可以在Selenium WebDriver协议中进行任何操作.

Once the test is in a web view context the command set that is available is the full Selenium WebDriver API.

一旦测试在web view 环境中可以用命令设置提供完整的Selenium WebDriver API.

##### Entering the web view context #####

进入web view环境

Here are the steps required to talk to a web view in your Appium test:

这里是Appium测试中于web view对话所需步骤：

1.Navigate to a portion of your app where a web view is active

导航到你的程序的一个web view活动的部分.

2.Retrieve the currently available contexts

检索当前可用的环境

*  This returns a list of contexts we can access, like `'NATIVE_APP'` or `'WEBVIEW_1'`

这里返回我们可以访问的环境列表,类似于'NATIVE_APP'or'WEBVIEW_1'

3.Set the context with the id of the context you want to access

设置你想访问的环境的id设置环境

*  This puts your Appium session into a mode where all commands are interpreted as being intended for automating the web view, rather than the native portion of the app. For example, if you run `getElementByTagName`, it will operate on the DOM of the web view, rather than return native elements. Of course, certain WebDriver methods only make sense in one context or another, so in the wrong context you will receive an error message.

这将使你的Appium进入session模式所有指令都被解释为用于自动化web view，
    而不是app的本地部分.
    例如，
    如果你运行'getElementByTagName',
    它将在web view中运行，
    而不是返回本机元素.
    当然，
    确定WebDriver的方法只能在一个环境或另外的环境中使用，
    因此在错误环境中你将收到错误消息.

4.To stop automating in the web view context and go back to automating the native portion of the app, simply set the context again with the native context id (generally `'NATIVE_APP'`) to leave the web context and once again access the native commands.

要停止自动化测试在web view环境中并返回自动运行app的本机部分，
    只要再次环境设置的本地环境id(generally(通常) 'NATIVE_APP') 
    离开web环境并且再次访问本机命令.

##### Automatically entering the web view context on session start #####

在启动会话时自动输入web view环境

If your application begins in a web view, and you do not want to automate the native application before entering it, you can have Appium automatically enter the web view context on session initialization by setting the `autoWebview` desired capability to `true`.

如果你的应用以web view开始，
    并且你不想在启动它之前去自动执行本地应用，
    你可以通过Appium 自动地进入web view环境
    在会话初始时通过设置'autoWebview'的需求为'true'.

##### Examples #####

<table> 
 <thead> 
 <tr> 
 <th align="left"></th> 
 <th align="left"></th> 
 </tr> 
 </thead> 
 <tbody> 
 <tr> 
 <td align="left">Java</td> 
 <td align="left">// assuming we have a set of capabilities driver = new AppiumDriver(new URL(<code>"http://127.0.0.1:4723/wd/hub"</code>), capabilities); Set contextNames = driver.getContextHandles(); for (String contextName : contextNames) { System.out.println(contextName); //prints out something like NATIVE_APP \n WEBVIEW_1 } driver.context(contextNames.toArray()[1]); // set context to WEBVIEW_1 //do some web testing String myText = driver.findElement(By.cssSelector(<code>".green_button"</code>)).click(); driver.context(<code>"NATIVE_APP"</code>); // do more native testing if we want driver.quit();</td> 
 </tr> 
 <tr> 
 <td align="left">Python</td> 
 <td align="left"># assuming we have an initialized <code>driver</code> object for an app # switch to webview webview = driver.contexts.last driver.switch_to.context(webview) # do some webby stuff driver.find_element(By.CSS, <code>".green_button"</code>).click # switch back to native view driver.switch_to.context(driver.contexts.first) # do more native testing if we want driver.quit()</td> 
 </tr> 
 <tr> 
 <td align="left">Javascript</td> 
 <td align="left">// assuming we have an initialized <code>driver</code> object for an app driver .contexts().then(function (contexts) { // get list of available views. Returns array: [“NATIVE_APP”,“WEBVIEW_1”] return driver.context(contexts[1]); // choose the webview context }) // do some web testing .elementsByCss(<code>'.green_button'</code>).click() .context(<code>'NATIVE_APP'</code>) // leave webview context // do more native stuff here if we want .quit() // stop webdrivage</td> 
 </tr> 
 <tr> 
 <td align="left">Ruby</td> 
 <td align="left"># assuming we have a set of capabilities @driver = Appium::Core.for(url: SERVER_URL, desired_capabilities: capabilities).start_driver # ruby_lib # opts = { caps: capabilities, appium_lib: { custom_url: SERVER_URL }} # @driver = Appium::Driver.new(opts, true).start_driver # I switch to the last context because its always the webview in our case, in other cases you may need to specify a context # View the appium logs while running @driver.contexts to figure out which context is the one you want and find the associated ID # Then switch to it using @driver.switch_to.context(“WEBVIEW_6”) Given(/^I switch to webview<code>$</code>/) do webview = @driver.available_contexts.last @driver.switch_to.context(webview) end Given(/^I switch out of webview<code>$</code>/) do @driver.switch_to.context(@driver.contexts.first) end # Now you can use CSS to select an element inside your webview And(/^I click a webview button $/) do @driver.find_element(:css, <code>".green_button"</code>).click end</td> 
 </tr> 
 <tr> 
 <td align="left">PHP</td> 
 <td align="left">// assuming we have an initialized <code>driver</code> object in an AppiumTestCase public function testThings() { $expected_contexts = array( 0 =&gt; <code>'NATIVE_APP'</code>, 1 =&gt; <code>'WEBVIEW_1'</code> ); $contexts = $this-&gt;contexts(); <code>$</code>this-&gt;assertEquals($expected_contexts, $contexts); t h i s − &gt; c o n t e x t ( this-&gt;context( this−&gt;context(contexts[1]); $context = $this-&gt;context(); $this-&gt;assertEquals(<code>'WEBVIEW_1'</code>, $context); // do webby stuff $this-&gt;context(<code>'NATIVE_APP'</code>); // domobile stuff }</td> 
 </tr> 
 </tbody> 
</table>

##### Automating hybrid Android apps #####

Appium comes with built-in hybrid support via Chromedriver, which allow the automation of any Chrome-backed Android web views.

Appium附带`built-in hybrid support via Chromedriver`,
    它允许任何Chrome-backed（backed：支持） Android web view的自动化.

There is an additional step necessary within your app build, unfortunately. As described in the Android remote debugging docs it is necessary to set to `true` the setWebContentsDebuggingEnabled property on the android.webkit.WebView element.

在你的app必要的内部构建中这是一个额外的步骤，不幸的是.
    如上在Android'remote debugging docs'所述必须
    将'android.webkit.WebView'的 'setWebContentsDebuggingEnabled'
    元素属性设置为'true'.

Once you have set your desired capabilities and started an Appium session, follow the generalized instructions above.

一旦你设置了你的`desired capabilities`并且开始一个Appium session，
    按照上面的详细说明.

##### Automating hybrid iOS apps #####

To interact with a web view Appium establishes a connection using a custom remote debugger. When executing against a simulator this connection is established directly as the simulator and the Appium server are on the same machine. Appium can automate WkWebView and UIWebView elements. Unfortunately, it is not currently able to handle SafariViewController elements.

为了与一个web view 交互
    Appium用自定义远程调试器建立连接.
    当对一个模拟器执行时
    这个连接是建立直接与模拟器并且Appium server是在同一台机器上.
    Appium可以自动化'WkWebView and UIWebView'元素.
    不幸的是，它目前不可以处理'SafariViewController'元素

Once you’ve set your desired capabilities and started an Appium session, follow the generalized instructions above.

一旦你设置了你的`desired capabilities`并且开始一个Appium session，
    按照上面的详细说明.

##### Execution against an iOS real device #####

对iOS真机上执行

When executing against an iOS real device, Appium is unable to access the web view directly. Therefore the connection has to be established through the USB cable. Appium can establish the connection natively since version 1.15 via appium-ios-device. ios-webkit-debugger-proxy is only necessary for Appium below version 1.15.

在对iOS real device执行时，
    Appium无法访问web view.
    因此需要连接已经确认的USB缆线连接.
    Appium可确认连接本地Appium-iOS-device从版本1.15开始.
    ios-webkit-debugger-proxy仅使用版本1.15以下的版本.

For instruction on how to install and run ios-webkit-debugger-proxy see the iOS webkit debug proxy documentation.

关于如何安装和运行'ios-webkit-debugger-proxy'
    参阅 iOS webkit debug proxy文档.

Now you can start an Appium test session and follow the generalized instructions above.

现在你可以开始Appium测试会话并按照以上说明进行操作.