Automation Guide
Application testing
Mobile testing
Testing mobile web applications
Testing Google Chrome on Android 
The requested page is not available for selected version.
Invoking Google Chrome on Android during automation
There are two methods by which Chrome may be invoked on Android devices.
- The “real-world” method: that is, simulate a manual tap on the Chrome icon on the device.
- Use the navigate built-in action.
Remember:
- For method #2, it is essential that you include the protocol (http:// or https://) for the target URL in the location argument. (For example, http://google.com)
- Regardless of the method chosen, ensure that the USB cable connection between your Android device and the host controller is always maintained during automation.
Note:
When Chrome on Android has multiple tabs open, navigate needs to traverse through those tabs to check for the already-navigated site. Activating each tab can typically take around two seconds. Consequently, the time consumed by navigate when many tabs are open can be significant.