Invoking Google Chrome on Android during automation

This feature is on-demand support

There are two methods by which Chrome may be invoked on Android devices.

  1. The “real-world” method: that is, simulate a manual tap on the Chrome icon on the device.
  2. 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.


Copyright © 2024 LogiGear Corporation. All rights reserved. LogiGear is a registered trademark, and Action Based Testing and TestArchitect are trademarks of LogiGear Corporation. All other trademarks contained herein are the property of their respective owners.

LogiGear Corporation

1730 S. Amphlett Blvd. Suite 200, San Mateo, CA 94402

Tel: +1 (650) 572-1400