Android phone (real device)
Test on a physical Android device, discovered via adb, added as a profile with one click.
A physical Android phone or tablet is discovered automatically and turned into a profile with one click, from the Add-device dialog or from the Android devices list on the Devices page.
Preconditions: Developer options and USB debugging enabled on the device; connected via USB (accept the debugging prompt on the phone), or reachable wirelessly.
Create it
- Plug the device in.
- Add device → An Android device. The dialog lists the phones this computer can see, and says what to fix when it sees none, use the rescan button after you fixed it.
- Optionally fill in Name, Description and Prompt above the list, the same fields every other kind has; an empty name means the phone's model.
- Click Add as device next to the phone, the device becomes a regular profile card, bound to its serial, and the dialog closes.
The same phone also appears under Android devices on the Devices page, where Details shows what was discovered (model, Android version, state) and Add as device does the same thing.
Run it
- Connect the profile card.
- Pick the profile in the test's Run on dropdown and press Run.
Keep the device awake and unlocked during runs, the agent acts on the real screen.
Wireless
No USB: enable wireless debugging on the device, then enter its ip:port in
the Wi-Fi field of the Add-device dialog, or in the field next to Connect
wireless on the Devices page. The device joins the list and can be added as
a profile the same way.
A device shown as offline or unauthorized can't be added, reconnect the
cable and accept the debugging prompt on the device.
No adb on this computer
Talking to a phone needs Google's adb tool. When it is not installed, the
An Android device entry of the Add-device dialog lists no phones and says
Android tools are not installed on this computer, followed by what will be
installed and an Install button.
Install runs the same Android SDK setup as the
Android emulator and the Android SDK card
in Settings: a dialog asks you to accept the Android SDK licences and start the
download, shows the progress, and can be stopped. The set it installs
(command-line tools, a JDK, the emulator, platform-tools and a system image,
about 1–1.5 GB in total) is the emulator's; adb is in platform-tools, so a
phone gets what it needs from the same folder. Prefer to install it yourself?
The dialog also shows the manual steps with the exact commands.
Once adb is there the phone list scans by itself, close the setup dialog and
your phone is in the list. A profile card whose adb has gone missing later
shows the same notice with Install, and Set up in place of Connect.