Testing Google Chrome on Android

With TestArchitect, automated tests may be created and run on web applications running within Chrome for Android.

  • Testing Chrome Android must be done by means of a USB cable connection.
  • The Android mobile device under test may be a physical device or an emulator.
  • Ensure that the Interface Viewer is closed prior to running automated tests.

Support Android emulators

  • Android SDK (Software Development Kit), which includes the Android Virtual Device (AVD) emulator that runs on your computer.

Supported Android versions

TestArchitect supports of the testing of web applications running within the Chrome browser on the following Android versions:

API levelAndroid OS version
API level 268.0
API level 247.0
API level 236.0
API level 225.1
API level 215.0.x
API level 194.4.x
API level 184.3.x
API level 174.2.x
API level 164.1.x
API level 154.0.3 - 4.0.4
API level 144.0 - 4.0.2

Supported web browser

TestArchitect supports testing on Google Chrome browser, up to version 86.

Technological approach

  • Remote debugging is a remote web inspector for debugging web applications on Android devices. The following configurations must be set up to allow remote debugging to be performed:

    • Physically connect the Android device to the TestArchitect controller via USB cable during test automation.
    • Install TestArchitect Agent.
  • Event-fired action model: TestArchitect attempts to effectuate built-in actions in a manner that is as close as possible to real user actions. In most cases, for each given UI action, TestArchitect calls a sequence of events as follows. (Refer to List of supported built-in actions for Chrome on Android.)

    Built-in actionsApplicable controlsSequence of events triggered
    click, tapall controlstouchstart > touchend > mouseover > mousedown > focus > mouseup > click
    click table celltabletouchstart > touchend > mouseover > mousedown > focus > mouseup > click
    set list checkul, oltouchstart > touchend > mouseover > mousedown > focus > mouseup > click
    select, click list itemselect-one, select-multipleclick > change
    setinput-checkbox, input-radiotouchstart > touchend > mouseover > mousedown > focus > mouseup > click
    enter, setinput-text, input-password, input-search, input-tel, input-url, input-email, input-numberkeydown > keypress > input > keyup > change

Google Chrome Android testing prerequisites
Guides to setting up Chrome Android automation under TestArchitect.

Invoking Google Chrome on Android during automation
There are two methods by which Chrome may be invoked on Android devices.

Identifying mobile UI controls
Device Live Screen extends to mobile apps the functionality of the Interface Viewer’s point-to-identify feature, streamlining the process of locating a given control within the Viewer’s UI Explorer tree.

Handling JavaScript popups on Chrome Android
TestArchitect offers a special set of actions for interfacing with JavaScript popups, which include alerts, prompts and confirmation dialogs.

List of supported Google Chrome Android built-in actions
Built-in actions supported by TestArchitect for testing Chrome on Android.

Limitations and workarounds of testing Chrome on Android
This topic categorizes some limitations you might encounter in testing web applications in Android Chrome. Applicable workarounds, if available, are also discussed.

Copyright © 2021 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(800) 322-0333