Preparing Test Computers and TestComplete for Android Testing

1. Install JDK

2. Install the Android SDK

3. Enable TestComplete Plugins

4. Enable USB Support in TestComplete Virtual Machine

5. Install Device USB Drivers

6. Specify Android SDK and Java Paths in TestComplete Settings

7. Add “Show Mobile Screen” Toolbar Button

8. Close Other TestComplete and TestExecute Instances

Other Preparatory Actions

To test Android applications, you need to have Java Runtime Environment or Java Development Kit (JRE or JDK) ver. 6 - 8 installed on the computer where TestComplete is installed. You can download it from –

http://java.com/en/download/windows_manual.jsp

For testing, it is enough to have JRE installed, but you may need to download and install JDK, as JDK includes JRE modules.

If you use a 64-bit version of Windows, you can use both the 32-bit and 64-bit Java versions.

If using the 64-bit Java version is not critical for you, we recommend installing the 32-bit Java version. Some packages of the Android SDK (that should also be installed on your test machine, see below) work with 32-bit Java.

After you install JDK, you need to specify the path to it in TestComplete settings (see below).

TestComplete uses the following modules of the Android SDK:

• Android Debug Bridge (ADB, adb.exe) - To communicate with Android devices.

• Android Asset Packaging Tool (aapt.exe) - To work with packages.

You need to have the Android SDK installed on each computer where you are going to create or run mobile tests.

You can get the Android SDK from the Android Developer web site:

https://developer.android.com/sdk/index.html

Android Studio (Default Download)

SDK Tools

You can test mobile applications with TestComplete only if you have an active license for the TestComplete Mobile module. In addition, the following plugins must be enabled in TestComplete:

Click the image to enlarge it.

• Mobile Support - Provides basic features for mobile testing.
• Android Support - Provides support for interacting with Android devices, virtual machines and emulators.

The plugins are installed and enabled automatically during TestComplete installation.

You can check to see if the plugins are active by selecting File > Install Extensions from the TestComplete main menu. If one of these plugins is not available, you need to run TestComplete installation in Repair mode. For more information on changing the installed TestComplete features, see Installing Extensions.

TestComplete can run on virtual machines. If you are using a physical mobile device for testing, the TestComplete virtual machine needs USB support to be able to access physical devices connected to the host computer. For instructions on how to enable USB support in a virtual machine, refer to the virtual machine’s documentation.

Applications typically run slower on virtual machines than on physical machines. To use TestComplete on a virtual machine, make sure your host configuration provides the highest virtual machine performance possible. If you experience performance issues, use more powerful host hardware.

TestComplete can automate tests on physical mobile devices that are connected to the computer via USB cable. For that you need to install the device USB driver on the TestComplete computer:

1. In the Get OEM drivers table in the Android documentation, find the USB driver that is appropriate for your mobile device:

   https://developer.android.com/studio/run/oem-usb.html#Drivers

   Note:

   If you are using a Google Nexus device, use the Google USB driver.

2. Download the needed driver from the vendor's web site.

3. Follow the instructions in the Android documentation to install the driver:

   https://developer.android.com/studio/run/oem-usb.html

To check whether the needed driver is installed and functions properly, you can use the Android Debug Bridge utility:

1. Connect your Android device to your computer via a USB cable.

2. Command the Android Debug Bridge utility to list the devices connected to your computer:

   adb devices

3. If the utility detects your device correctly and shows its serial number, the driver is installed and functions properly.

Before you start creating mobile tests, specify the Android SDK and Java paths in TestComplete.

When you install TestComplete, the installation program tries to find these paths automatically on your computer. If it is unable to do so, you may need to specify these paths in TestComplete manually:

Click the image to enlarge it.

1. From the TestComplete main menu, select Tools > Options. This will open the Options dialog.

2. On the left of the dialog, select the Engines > Mobile > Android category.

   Note:

   This category is available only if the Android Support plugin is installed and enabled in File > Install Extensions.

3. In the Path to Android SDK edit box, specify the folder where you installed the Android SDK on your computer. For example, C:\Android SDK.

4. In the Path to Java Runtime edit box, specify the folder where Java is installed on your computer. For example, C:\Program Files\Java\jre8.

5. Click OK to close the dialog and save the settings.

To create Android tests, you use the TestComplete built-in Mobile Screen window. It displays the screen of the connected mobile device and lets you manipulate the device remotely.

By default, the Show Mobile Screen command is on the Test Engine toolbar. If the command is not available, add it to the toolbar manually:

1. Right-click within the toolbar area and select Customize from the context menu.

2. In the Customize dialog, switch to the Commands tabbed page.

3. Select Mobile in the category list on the left and then drag the Show Mobile Screen item to a toolbar.

   

   When done, close the dialog.

When testing Android applications, do not run TestComplete and TestExecute at the same time on a computer (in the same Windows session, or in different sessions in Windows Server editions). Otherwise, the two Android testing engines will conflict and cause unexpected behavior.

After you prepared TestComplete for testing, you need to check settings of your mobile device and application under test.