Known issues when running mobile tests

This topic contains troubleshooting and limitation information when running tests using OpenText Functional Testing Lab.

In this topic:

Selecting devices and launching browsers

To avoid errors, ensure that the methods used to lock your device and launch a browser on the same device are consistent between your Record and Run Settings and your test steps.

For more details, see the LaunchBrowser and LaunchMobileBrowserWithID method documentation in the OpenText Functional Testing Object Model Reference.

Switching between the Device Capabilities and Specific Device tabs

Sometimes, when configuring the Record and Run Settings in OpenText Functional Testing, if you switch between the Device Capabilities and the Specific Device tab, and then click the Open in Functional Testing Lab button to open the OpenText Functional Testing Lab wizard, the wizard opens the Device capabilities tab.

Workaround: Do one of the following:

• With the specific device tab open, click OK to close the Record and Run Settings tab. Then open the Record and Run Settings dialog box again and click the Open in Functional Testing Lab button to open the OpenText Functional Testing Lab tab.

• Select the specific device from the Specific device tab in the Record and Run Settings dialog box

Multiple devices in test runs

Unexpected issues may occur when you are running a test with a MobileWebView test object on multiple devices.

If so, remove the accessibilityid description property from the test object and run the test again.

Device filtering in test runs: Testing multiple devices

If you have multiple steps in your test that use the same device filtering criteria defined by description properties, and also have multiple devices connected to OpenText Functional Testing Lab that match the filtering criteria, all relevant steps use the same device used by the first step in your test.

To use a different device in a specific step, modify the filter for that step.

Device filtering in test runs: Modifying your filter

If your device filter is defined by description properties, and you modify those properties before running the test a second time, the device remains locked from the first run, and the second test run will fail.

Unlock the device in OpenText Functional Testing Lab before running the test a second time.

Device filtering in test runs: Multiple steps with different device filters

If your test has separate steps with different device filters for each step, where the device filters do not conflict (the same device matches each filter), and:

• You have multiple matching devices connected. A different device is selected for each step.
• You have only one matching device connected. The test fails the second time the device is selected.

To use the same device, modify the filter so that the properties match in all relevant steps.

For example, if you have a single device connected that matches the filters in both of the following steps, the test will fail on the second step.

Device("osversion:=8.4","ostype:=iOS").App("name:=MC Browser","identifier:=com.hp.HPMobileWebBrowserINJ").MobileEdit("nativeclass:=UITextField","mcindex:=0","ispassword:=False","class:=Input","accessibilityid:=url").Set "AAA"

Device("ostype:=iOS").App("name:=MC Browser","identifier:=com.hp.HPMobileWebBrowserINJ").MobileEdit("nativeclass:=UITextField","mcindex:=0","ispassword:=False","class:=Input","accessibilityid:=url").Set "BBB"

Modify the steps as follows to run the test:

Device("ostype:=iOS").App("name:=MC Browser","identifier:=com.hp.HPMobileWebBrowserINJ").MobileEdit("nativeclass:=UITextField","mcindex:=0","ispassword:=False","class:=Input","accessibilityid:=url").Set "AAA"

Device("ostype:=iOS").App("name:=MC Browser","identifier:=com.hp.HPMobileWebBrowserINJ").MobileEdit("nativeclass:=UITextField","mcindex:=0","ispassword:=False","class:=Input","accessibilityid:=url").Set "BBB"

Run results

Device logs

If you start recording with the Logs option cleared in the Device Metrics and then stop recording, but resume recording with the option selected, the Download device logs button (in the device Options pane) is not available.

Workaround: Press the Refresh button in the remote access window.

Visual Relation Identifier steps

If the first step in your test uses Visual Relation Identifiers (VRI) to identify an object, your app is not launched, installed, or restarted, even if defined to do so otherwise.

Workaround: Ensure that your app is launched, installed, or restarted before using VRI to identify a test object.

Fingerprint simulations

Step results for failed fingerprint simulations may show differently, depending on the app's configured behavior.

See also

• Known Issues - Mobile Add-in