[
https://issues.apache.org/jira/browse/CB-10652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15166486#comment-15166486
]
ASF GitHub Bot commented on CB-10652:
-------------------------------------
Github user dblotsky commented on a diff in the pull request:
https://github.com/apache/cordova-medic/pull/81#discussion_r54035101
--- Diff: SLAVES.md ---
@@ -38,6 +49,12 @@ To make the Android commands available on the command
line, set the following en
- `ANDROID_HOME`, equal to the absolute path to the Android SDK directory
- `PATH`, extended to contain `ANDROID_HOME/tools` and
`ANDROID_HOME/platform_tools`
+To run Appium tests, you may also need to download the [latest
chromedriver](https://sites.google.com/a/chromium.org/chromedriver/downloads)
and set the following environment variable:
+
+- `CHROMEDRIVER_EXECUTABLE`, equal to the absolute path to the
chromedriver executable
+
+This is needed to avoid the bug in older chromedriver versions that was
preventing Appium tests to switch contexts. There are a bunch of github issues
created for this bug in Appium project:
[1](https://github.com/appium/appium/issues/4429),
[2](https://github.com/appium/appium/issues/5526),
[3](https://github.com/appium/appium/issues/5616).
--- End diff --
Please make the links reference links.
> Add a documentation on how to set up slaves for Appium tests
> ------------------------------------------------------------
>
> Key: CB-10652
> URL: https://issues.apache.org/jira/browse/CB-10652
> Project: Apache Cordova
> Issue Type: Task
> Components: Medic
> Reporter: Alexander Sorokin
> Assignee: Alexander Sorokin
>
> Current documentation lacks the description of workaround for chromedriver
> bug and installing ios-webkit-debug-proxy.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
