Selenium WebDriver Language Bindings
The standard selenium project WebDriver language bindings need to be installed for your language of choice for writing your tests. This library is available from your friendly local package manager or the selenium project (https://www.seleniumhq.org/download/). For example, the language bindings for Python can be installed with pip.
As of Chrome version 33, a rooted device is no longer required. If running tests on older versions of Chrome, devices needed to be rooted as ChromeDriver required write access to the /data/local directory to set Chrome's command line arguments.
1. Start the Android SDK's Android Debug Bridge (adb) server:
2. If testing on Chrome app prior to version 33, ensure adb shell has read/write access to /data/local directory on the device:
3. It is generally recommended that you start ChromeDriver through the Selenium library, though you can also manually start it from the command line. See Getting started for more information.
The following Chrome Options are applicable to both Chrome and WebView apps:
androidPackage: The package name of the Chrome or WebView app.
androidDeviceSerial: (Optional) The device serial number on which to launch the app (See Multiple Devices section below).
androidUseRunningApp: (Optional) Attach to an already-running app instead of launching the app with a clear data directory.
The following capabilities are only applicable to WebView apps.
androidActivity: Name of the Activity hosting the WebView.
androidProcess: (Optional) Process name of the Activity hosting the WebView (as given by ps). If not given, the process name is assumed to be the same as androidPackage.
Running a Test
Tests should pass the app’s package name to the ChromeDriver through the androidPackage option. For example, a minimal Python test looks like this:
To use a particular device for a session, specify androidDeviceSerial as a Chrome option.
If the serial number is not specified, the server will select an unused device at random to associate with each session. An error will be returned if all devices already have active sessions, so tests should make sure to call quit when finished.
If your tests expect to connect to wd/hub, you can add --url-base=wd/hub when launching the server: