You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cordova.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2016/02/16 14:29:18 UTC
[jira] [Commented] (CB-10619) Appium tests fail to switch context
to webview on Windows slave's Android emulator
[ https://issues.apache.org/jira/browse/CB-10619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15148584#comment-15148584 ]
ASF GitHub Bot commented on CB-10619:
-------------------------------------
GitHub user alsorokin opened a pull request:
https://github.com/apache/cordova-plugin-camera/pull/171
CB-10619 Appium tests: Properly switch to webview
https://issues.apache.org/jira/browse/CB-10619
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/MSOpenTech/cordova-plugin-camera CB-10619
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/cordova-plugin-camera/pull/171.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #171
----
commit 61b77951e11cfdae8eaf5e6b2f8392b4822239f5
Author: Alexander Sorokin <al...@akvelon.com>
Date: 2016-02-16T13:28:43Z
CB-10619 Appium tests: Properly switch to webview
----
> Appium tests fail to switch context to webview on Windows slave's Android emulator
> ----------------------------------------------------------------------------------
>
> Key: CB-10619
> URL: https://issues.apache.org/jira/browse/CB-10619
> Project: Apache Cordova
> Issue Type: Bug
> Components: Medic
> Reporter: Alexander Sorokin
> Assignee: Alexander Sorokin
>
> Here's a log sample
> {noformat}
> > RESPONSE init({"browserName":"","appium-version":"1.3","platformName":"Android","platformVersion":19,"deviceName":"Galaxy_Nexus","app":"C:\\Users\\buildbot\\slaves\\apache\\cordova-android-win\\mobilespec\\platforms\\android\\build\\outputs\\apk\\android-debug.apk","autoAcceptAlerts":true}) "7dc6d1dd-d4ef-41aa-ac32-a3400d333e6b",null
> > CALL setImplicitWaitTimeout(10000)
> > POST /session/:sessionID/timeouts/implicit_wait {"ms":10000}
> > RESPONSE setImplicitWaitTimeout(10000)
> > CALL sleep(20000)
> > RESPONSE sleep(20000)
> > CALL sleep(10000)
> > RESPONSE sleep(10000)
> [MEDIC LOG Mon, 15 Feb 2016 07:54:00 GMT] Spec passed: camera.ui.util configuring driver and starting a session
> [MEDIC LOG Mon, 15 Feb 2016 07:54:00 GMT] Starting new spec: camera.ui.spec.1 Saving the picture to photo library
> > CALL context("WEBVIEW")
> > POST /session/:sessionID/context {"name":"WEBVIEW"}
> > CALL context("WEBVIEW")
> > POST /session/:sessionID/context {"name":"WEBVIEW"}
> > CALL elementById("middle")
> > POST /session/:sessionID/element {"using":"id","value":"middle"}
> [MEDIC LOG Mon, 15 Feb 2016 07:59:20 GMT] Spec failed: camera.ui.spec.1 Saving the picture to photo library
> [MEDIC LOG Mon, 15 Feb 2016 07:59:20 GMT] Starting new spec: camera.ui.spec.2 Selecting only videos
> > CALL context("WEBVIEW")
> > POST /session/:sessionID/context {"name":"WEBVIEW"}
> > CALL context("WEBVIEW")
> > POST /session/:sessionID/context {"name":"WEBVIEW"}
> > CALL elementById("middle")
> > POST /session/:sessionID/element {"using":"id","value":"middle"}
> > CALL execute("var info = document.createElement(\"div\"); info.id = \"info\"; document.body.appendChild(info);")
> > POST /session/:sessionID/execute {"script":"var info = document.createElement(\"div\"); info.id = \"info\"; document.body.appendChild(info);","args":[]}
> An error occured: [execute("var info = document.createElement(\"div\"); info.id = \"info\"; document.body.appendChild(info);")] Error response status: 6,
> Failing with message: [execute("var info = document.createElement(\"div\"); info.id = \"info\"; document.body.appendChild(info);")] Error response status: 6,
> [MEDIC LOG Mon, 15 Feb 2016 07:59:20 GMT] Spec failed: camera.ui.spec.2 Selecting only videos
> {noformat}
> Upon initial investigation I found that it is a bug in chromedriver:
> https://github.com/appium/appium/issues/5616
> It has been fixed in a new chromedriver version but Appium didn't bundle it yet.
> As a temporary workaround we can specify "chromedriverBinary" as a desired capability when starting appium session and point it to a newer chromedriver binary.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@cordova.apache.org
For additional commands, e-mail: issues-help@cordova.apache.org