Connect emulators

Emulators let you install and replay tests on emulated devices. OpenText Functional Testing Lab lets you test your devices using some of the popular emulators.

The supported emulators are Genymotion and Android SDK.

If you are using OpenText Functional testing, you can also record and run Web tests using the Chrome emulator. For details, see Define settings for testing Web applications using the Chrome emulator.

Setting up an Android Emulator - Windows

This section describes how to set up AVD (Android Virtual Device) emulators on a Windows server or connector machine.

To create and launch an AVD emulator:

Make sure your machine meets the requirements for Android Studio. For details, see the Android Developers documentation.
Download Android Studio from the Android Studio download page.
Run the setup, and include the Android Virtual Device (AVD) component. This component enables you to create a profile of a virtual device that can then be run on the Windows host and connected to the OpenText Functional Testing Lab server using a device connector.
From the Tools menu, select AVD Manager to open the AVD Manager.
In the AVD manager, create a virtual device or choose a predefined device. For details, see create and manage virtual devices in the Android Developer documentation.
To run an emulator that uses an AVD, double-click it or click Launch.
The device appears in the lab as disconnected.
The agent is loaded automatically on the device. In the agent, switch on the Service if needed.
In the OpenText Functional Testing Lab Device Lab, click refresh. The virtual device should appear in the mobile lab as an available test device. If it does not, stop the device by closing its window. Restart the connector. After the connector has started, restart the device emulation. Make sure that the filter is not hiding emulated devices.

Setting up the SDK Emulator - Linux

Emulators on Linux are supported only using the command line.

Download the Android SDK Manager for Linux from the Android Studio site. Scroll down to the Command line tools only section, and download the command lines tool package for Linux.
Extract the contents of the zip file.
Under the tcmdline-tools/bin folder, locate the sdkmanager tool.
Run sdkmanager --update [options] to update all installed packages. We also recommend to run sdkmanager --"platform-tools" "platforms;android-28" to install the latest platform tools, including adb. For details, see command line documentation in the Android developers documentation.
Under the cmdline-tools/bin folder, locate the avdmanager tool. The AVD manager enables you to create a profile of a virtual device that can then be run on the Linux host and be accessed using the device connector. Run the line command to create a new profile for the device you want to emulate, for example, avdmanager create avd -n test -k "system-images;android-25;google_apis;x86". For details, see the command line documentation in the Android Developers documentation.

The device should now appear in the list of existing virtual devices. For details, see Manage devices.

Create a test with an emulator

To prepare a test through an emulator:

Install your emulator. Prepare your environment as described by your emulator's documentation.
When using Genymotion, configure the adb using the same settings as you used when installing the connector. In Genymotion, select Settings > ADB tab > Use custom Android SDK tools.
- If you have an ANDROID_HOME environment variable, use the same adb path as you used when setting up the connector for Use custom Android SDK tools in Genymotion.
- If you do not have an ANDROID_HOME environment variable, the connector uses the embedded adb tools. Set the Use custom Android SDK tools to <Functional Testing Lab for Mobile and Web Connector>\connector\android-sdk-windows.
Start the emulator. Choose the device to emulate.
Select an emulated device within your testing tool in the Device selection area.
Perform actions on the app on the emulated device.

Install SDK tools and emulator images manually

The default installation of the connector does not include the SDK emulator tools. If you would like to install the emulator on your Connector machine, perform the following steps:

Download the Android SDK Tools package from the Android SDK website. We recommend SDK version 25.2.2.
Extract the contents of the zip file to a folder named tools. Copy the newly created tools folder to the android-sdk-windows/ android-sdk-linux subfolder of the connector's installation folder.
Open the tools folder and double-click the Linux shell command.
If you are accessing the SDK manager through a proxy server, enter the proxy information:
1. Select Tools > Options to open the Settings dialog box.
2. Enter the HTTP Proxy Server and Proxy Port values.
3. Click Close.
In the Android SDK Manager window, choose the emulator images to install under the Tools node. Note that each Android version has its own image.

Tip: Use Intel x86 base images for better performance on machines that support Intel HAXM (Hardware Accelerated Execution Manager).
In the SDK Manager Appearance & Behavior > System Settings > Android SDK > SDK Updates Sites tab, select Intel HAXM and click apply.
Click OK to install the selected packages.
Continue with opening the AVD to select devices, as described in Setting up an Android Emulator - Windows.

Working with Genymotion Desktop emulated devices

This section is not relevant for OpenText Core SDP and OpenText Core Functional Testing Lab.

When you integrate with on-premises Genymotion emulator, OpenText Functional Testing Lab shows the devices in the lab.

The following are the prerequisites for integration with Genymotion Desktop emulated devices:

A valid Genymotion desktop license
A Genymotion desktop installation on a Windows machine with OpenText Functional Testing Lab server
An environment that supports the Genymotion gmsaas tool.

To set up the Genymotion desktop integration:

Make sure you have installed the Genymotion client on the OpenText Functional Testing Lab server. Only a Genymotion Windows client is supported. Sign in with your Genymotion credentials and register your license. For details, see the Help menu on the Genymotion website.
Configure Genymotion to use the OpenText Functional Testing Lab ADB folder:
1. In the Genymotion client settings, click the ADB tab and select Use custom Android SDK tools.
2. Click Browse and locate the android-sdk-windows folder. The default folder is C:\Program Files\Functional Testing Lab for Mobile and Web Server\server\android-sdk-windows.
3. Make sure that the dialog box indicates Android SDK tools found successfully.
In Genymotion Desktop, start one or more virtual devices.
Open the Device Lab tab to view the Genymotion virtual devices. (This may take several minutes.) For details, see Connect a Genymotion Cloud emulator.

Genymotion Cloud integration

This section is not relevant for OpenText Core SDP.

With the Genymotion Cloud integration, you can access emulated Android devices on the Genymotion Cloud from your lab.

When you integrate with Genymotion Cloud, two virtual emulator devices, representing two common Genymotion templates, are shown in the lab.

Note that this integration is currently supported only with a Windows connector. You can use the connector embedded in the OpenText Functional Testing Lab server, or a standalone connector.

Tip: You can add other Genymotion templates using the REST API.

Prerequisites

The following are the prerequisites for integration with Genymotion Cloud emulated devices:

A Genymotion Cloud trial or paid license
Make sure that there is no gmadbtunneld running on the connector through which OpenText Functional Testing Lab communicates with Genymotion Cloud.

Note: This integration is only available with a Professional, Trial, Enterprise, or Ultimate license. For more details, see Licenses.

To set up the Genymotion cloud integration:

Open the Genymotion Integration page in the Administration settings.

Provide the Genymotion Cloud username and password.
Select the connector through which OpenText Functional Testing Lab communicates with Genymotion Cloud, and provide proxy details if required.
Provide the Genymotion gmsaas install path on the connector or accept the default:
- Windows when using the connector on the server machine: <OpenText Functional Testing Lab installation>\server\gmHome\gmsaas, by default C:\Program Files\Functional Testing Lab for Mobile and Web Server\server\gmHome\gmsaas.
- Windows when using a standalone connector (not on the server machine): <OpenText Functional Testing Lab installation>\connector\gmHome\gmsaas, by default C:\Program Files\Functional Testing Lab for Mobile and Web Connector\connector\gmHome\gmsaas.
Click Verify and Save. If you turn off the integration or change the account settings, the virtual devices associated with the previous account are no longer available.

Open the Device Lab tab to view the Genymotion virtual devices. For details, see Connect a Genymotion Cloud emulator. To remove the emulated devices, turn off the integration in the Administration settings.

Slow network issues

If you are having difficulties connecting to the devices due to network issues, you can increase the timeout value.

Open the connector.properties file in the <Functional Testing Lab for Mobile and Web_Installation_folder>\< server|connector>\conf folder.
Search for common.config.appInstallTimeoutSecond. If it is missing, add it.
Increase its value. The default is 60 seconds.

Tips for Using the Android SDK Emulator

The Restart button in OpenText Functional Testing Lab is disabled for Android SDK emulator devices.
Certain apps cannot be installed on the SDK emulator with an ARM configuration. As a workaround:
- In most instances, it is recommended to work with Android SDK with HAXM.
- In the following instances use the ARM configuration:
- For recording, close the remote device window and record on the device.
- For replay, record on Genymotion or Android SDK x86 with HAXM, and replay in silent mode in OpenText Functional testing.
- Start the emulator in headless mode.
- Reduce the resolution of the device.

Troubleshooting and tips

Emulator support is provided for Android 4.1 and higher, and an API level of 19 or higher. For more information, see Device emulator issues.

The following guidelines apply:

When using an emulator for devices with Android 6.0 and higher, SMS and Call simulations are not supported.
In RHEL (Red Hat Enterprise Linux) environments earlier than RHEL 7, you cannot work with the remote screen viewer on emulators, because GPU acceleration is not supported (GPU acceleration is available on Windows machines, or Linux machines with RHEL 7 and higher.)
Emulation is not supported for apps that have full control of the adb, such as Wandoujia.