Dev Access

The Dev Access plugin (Android) and app (iOS) provide a user-friendly interface for connecting to and interacting with devices in the OpenText Functional Testing Lab device lab, from within your integrated development environment (IDE).

Supported devices

Dev access is not supported on iOS 17 devices, OpenText hosted public devices, ADF devices, WeTest devices, virtual devices, emulators and simulators.

Back to top

Install Dev Access for Android

This section explains how to install Dev Access for Android.

To connect to Android devices:

  1. Install the OpenText Functional Testing Lab Jetbrains plugin.

  2. Follow the steps for configuring the settings and connecting devices. For details, see Configure settings and Connect to lab devices

Note: For Android Studio Giraffe (2022.3.1) and later, use JDK version 17.0.10.

Back to top

Install Dev Access for iOS

This section explains how to install Dev Access for iOS devices.

To install Dev Access for iOS:

  1. To connect to iOS devices download the app from OpenText Functional Testing Lab as follows:
    1. Navigate to the Device Lab > Devices page. Hover over the device's card and click the Dev Access button, or in List view, select a device and click Dev Access.
    2. Select the Mac operating system and click Download.
  2. Extract the files on your IDE machine.
  3. Open Terminal and grant execution permission to the files by running the following command in the folder to which you extracted the files:
    sudo chmod –R 777 *

Back to top

Configure settings

Configure settings so that you can connect to the lab.

To configure settings:

  1. Make sure that have an execution key. If not, generate one. For details, see Generate and manage access keys.

  2. Open the plugin/app. For iOS, users with sudo permissions can double click dev-access-ui.command to open the dev access interface.
  3. In the Settings tab, provide the following:
    • URL for the OpenText Functional Testing Lab server and port.
    • Your execution key.
    • If connecting through a proxy server, specify the details of the proxy machine.
    • Android only: ADB execution file path. This is automatically detected from your IDE. Browse to select a different ADB version file if needed.
  4. Click Log in.

Back to top

Connect to lab devices

This section explains how to connect to a lab device so that you can interact with the device form within your IDE.

To connect a device:

  1. Select the Devices tab of the plugin/app.
  2. Enable the connection by clicking the Enable OpenText Functional Testing Lab Dev Access option.
  3. Select an OpenText Functional Testing Lab workspace. The list of devices allocated to that workspace and all shared devices are displayed.
    The Android plugin displays only Android devices. The iOS app displays only iOS devices.
  4. Select a device from the list, and click CONNECT DEVICE. Repeat this step to connect to multiple devices.
  5. When you connect to a lab device, the remote device view opens and you can interact with the device.


    Note: If the device screen is not displayed in the Remote Viewer tab of the plugin after connecting a device, use one of the following workarounds:

    • After connecting the device from the plugin, view and control the device by opening it remotely in a web browser from the Lab console.

    • Use a JDK with built-in Java FX for running the IDE:

      1. On the IDE machine, download the Azul Zulu JDK FX 17.48.15 (Java 17.0.10+7) zip from Azul Systems and extract it.

      2. In the IDE, open the Choose Boot Java Runtime for the IDE. In the New menu select Add Custom Runtime. Select Add JDK and select the zulu17.48.15-ca-fx-jdk17.0.10-win_x64 folder which is in the extracted folder (Windows) or the zulu-17.jdk folder (Mac). When prompted, click OK and restart the IDE.

  6. To end a device session, select the device in the list and click DISCONNECT DEVICE.

Local devices cannot be accessed while Dev Access is enabled. To switch back to your local devices, click the Disable OpenText Functional Testing Lab Dev Access option.

Back to top

Known issues

  • Dev access is not supported when shared spaces are enabled (multi tenancy).

Android:

  • Logcat plugin: Starting with Android Studio Giraffe (2022.3.1), you can no longer manage which version of logcat is used. With Android Studio Flamingo (2022.2.1) or earlier, you can still use an older logcat plugin tool version. Make sure that the Enable new logcat tool window checkbox is not selected.

  • Device Explorer: The Device Explorer is supported only on Android Studio Electric Eel (2022.1.1) and earlier versions.

  • When using the Dev access plugin with Android Studio using JDK 11 or above, the remote device viewer shrinks. This issue is caused by JavaFX not respecting the Windows OS scale.
    Workaround: In Settings >Display > Scale and Layout> Change the size of text, app, and other items change the scale to 100%.
  • When using JRE/JDK version 8u211/8u212/8u222, a white screen is displayed on the remote device viewer. This issue is resolved when using JDK 8u231

iOS:

  • If you launch Xcode after starting a session on an iOS device, the CPU usage for Dev Access reaches 100%.
  • macOS Catalina:
    • You may need to click multiple times on the DISCONNECT DEVICE button to stop a session.
    • You may be unable to paste access keys to the GUI tools.

See also: