Known Issues - Mobile Add-in

This topic contains troubleshooting and limitation information about working with the Mobile Add-in.

In this topic:

Getting started

Using Proxy servers

• Only proxy servers that support the WebSocket protocol are supported. For Apache servers, use version 2.4 or later.

• Basic authentication must be permitted on the port used by the proxy server.

  Apache configuration example:

  ###forward basic authentication###
  ProxyRequests on
  AllowCONNECT 8108 8080 80 7002 443 8443

• If the Camera or Video Simulation windows do not display the media files for sensor simulation steps when uploading media files from a URL, make sure to set the proxy settings in the Digital Lab pane of the Options dialog in OpenText Functional Testing (Tools > Options > GUI Testing tab > Digital Lab node).

Connecting to Digital Lab

If either your OpenText Functional Testing or Digital Lab sessions are invalid, due to license issues or timeout from the Digital Lab server, when clicking Test Connection in the Digital Lab pane of the Options dialog, OpenText Functional Testing gives you an operation timeout.

Workaround: Exit from OpenText Functional Testing and Digital Lab as necessary and make sure your licenses are correctly installed for the correct products. Then reconnect to OpenText Functional Testing and Digital Lab.

Multiple Digital Lab workspaces

The following known issues exist for selecting mobile apps and working with multiple workspaces:

• Selecting a specific app upload number is not supported from the OpenText Functional Testing Record and Run Settings dialog. Select the app and upload counter from the Digital Lab wizard instead.

• If the same app is uploaded to the shared assets, and also to another workspace, selecting the latest app upload version in the Record and Run Settings dialog will use the latest version between them, tagged with its workspace name.

• If the same app is uploaded to multiple workspaces, and OpenText Functional Testing does not specify a workspace or an app upload number, it will use the latest upload number of the app in any workspace on the system.

Back to top

General

OpenText Functional Testing text recognition and Digital Lab

• OpenText Functional Testing text recognition for mobile devices does not support the Tesseract OCR text recognition engine.

• OCR is supported only with image quality set to 100%.

Wildcards

If you use wildcards in your WebUtil.LaunchBrowser steps to perform a fuzzy search for devices, you must also provide an operating system.

For example, the following step may generate errors:

WebUtil.LaunchBrowser "MOBILE_SAFARI","iPhone","",""

Prevent errors by providing an operating system. For example:

WebUtil.LaunchBrowser "MOBILE_SAFARI","iPhone","","iOS"

Sensor simulation operations

• Uploading media files using drag and drop actions into a SimulateCamera or SimulateVideo operation is not supported.

• If the specified files required for the SimulateCamera or SimulateVideo methods are not correct in the test steps, the remote access window gives no indication of the operation being performed successfully or the failure or success of the step.

  Workaround: View the step details in the test results.

Localization

Amazon Web Services (AWS)

The following known issues exist when using Digital Lab with OpenText Functional Testing on AWS:

• Multiple devices are not supported in a single test running on AWS.

• Running business process tests of Web applications on mobile devices is not supported for devices on Amazon Web services.

Back to top

Spying and highlighting with Digital Lab

• When using the Object Spy, hovering over an object when using the Object Spy to view object properties is not supported. Click the object instead to view the properties.

• On slow websites, the first Spy action displays 'device:device' on low-performing devices.

  Workaround: Increase the 'MAX_JS_ENGINE_READY_CHECK_RETRIES' to 300 in connector.properties, and increase timeout duration for OpenText Functional Testing to 1 min.

• For native browsers and the MC Browser: When using the Object Spy on the web objects: Back, Forward, Refresh, and URL box, OpenText Functional Testing generates Device.app.xx, instead of Browser.page.xx.

  Workaround: Modify the code manually.

• Highlighting on Browser test objects shows some location deviation, using both the MC Browser and native browsers.

• When highlighting an object from the object repository, any non-default identification properties with incorrect values are ignored. This enables OpenText Functional Testing to highlight the control in the application.

• OpenText Functional Testing may not highlight a test object in the object repository in the following scenarios:

  Scenario	Workaround
  This is the first editing session after installing OpenText Functional Testing.	Define the relevant device and application in the Mobile tab of the Record and Run Settings dialog box. Then start and stop a recording session.
  This is the first editing session after restoring factory defaults in the Options dialog box.	Define the relevant device and application in the Mobile tab of the Record and Run Settings dialog box. Then start and stop a recording session.
  The Mobile tab of the Record and Run Settings dialog box is empty, and no device or application is selected.	Define the relevant device and application in the Mobile tab of the Record and Run Settings dialog box. Then start and stop a recording session.
  The remote access window displays a different device than the one defined in the Mobile tab of the Record and Run Settings dialog box.	Do one of the following: Define the relevant device and application in the Mobile tab of the Record and Run Settings dialog box. Then start and stop a recording session. Set the id property in the Device test object description to the value of the device that is open in the remote access window.

• If an object's description properties contain a space at the beginning or end of the property name, OpenText Functional Testing and Digital Lab cannot highlight the object.

  Workaround: Do one of the following:

  • Remove this property from the object description in the Object Repository in OpenText Functional Testing

  • Add a regular expression for the property ".*"

• When working with Web tests, spying is not supported on iOS devices in non-mobile optimization pages.

• Recording and highlighting on certificate related dialogs (from a Web page in a Mobile Web application) is not supported.

  Workaround: Add a step using descriptive programming to identify and perform user actions on the certificate dialogs in the test.

  In addition, you need to manually install the needed certificate on the device running the test before running the test.

Back to top

Recording on mobile devices

Back to top

Running OpenText Functional Testing tests with Digital Lab

This section includes the following issues:

• Selecting devices and launching browsers

• Switching between the Device Capabilities and Specific Device tabs

• Multiple devices in test runs

• Device filtering in test runs: Testing multiple devices

• Device filtering in test runs: Modifying your filter

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

• Run results

• Device logs
• Visual Relation Identifier steps
• Fingerprint simulations

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 Digital Lab button to open the Digital Lab wizard, the Digital Lab 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 Digital Lab button to open the Digital 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 Digital 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 Digital 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.

Back to top

Web testing

Native browsers on mobile devices

Using the MC Browser app with OpenText Functional Testing

Using the Chrome emulator on Digital Lab

Shadow Dom support

Running mobile tests on Shadow Dom web apps and iOS devices is only supported for:

• iOS versions 11 and higher
• Android with Chrome versions 56 and higher

Back to top

ALM and BPT

Working with ALM and Digital Lab

Business Process Testing and Digital Lab

• Using the Capture toolbar is not supported.

• When recording a business process test, if you press the Stop button when recording, you cannot start recording again.

• If you started the Mobile Web app from the HOME screen and started recording, operations performed on the page are recorded when no recorded steps are expected.

  The steps are recording using the following syntax:

  Browser(XXX).Navigate "XXX"

• Creating multiple application areas one right after another with settings defined on the Web or Mobile tabs retains the information from the earlier application area. Clear these settings to define your subsequent application area details from scratch.

• BPT does not support multiple application areas in a single test or flow.

  For example:

  Add the following components to your test or flow, each with a separate application area defined:

  Component 1 / Application area 1	iOS device AMB app
  Component 2 / Application area 2	Android device UiCatalog app

  During your test run, OpenText Functional Testing is not able to find the correct app to install on your second device, the Android.

Back to top

Specific types of apps

Working with native apps

OpenText Functional Testing cannot record or run steps on native mobile controls, such as a native date picker when working in a native browser or the MC Browser.

Workaround: Add the native mobile control to the object repository manually, and then manually add a step to operate the control.

For example:

1. Spy on a date picker control, and add the corresponding WebEdit object to the Object Repository.

2. Then add a step similar to the following to your test:

   Browser("Reservations").Page("Your Reservation").WebEdit("check-in-date").Click

Flutter-based apps

OpenText Functional Testing can record and run tests on packaged Android and iOS apps built using the Google Flutter SDK. The following object types are supported: MobileButton, MobileCheckBox, MobileEdit, MobileLabel, MobileObject,MobileTabStrip.

For details on the supported Flutter SDK version, and guidelines for preparing and uploading Flutter apps see the Digital Lab Help Center.

The following methods are not supported for flutter-based applications: SetSecure, Select, ChildObjects, MobileEdit.Set, MobileLabel.Set, MobileObject.SetFocus.

iOS, native, packaged apps and the ChildObjects method

If a ChildObject step is run on an iOS, native, packaged app (Device().App().MobileObject().childobjects()), and the MobileObject is not found, the step returns all childobjects on the current page being tested.

Working with hybrid apps

The following features are not supported when testing hybrid applications:

• Accessibility checkpoints

• Mobile optimization

  The following are supported only for web pages that are optimized for mobile:

  • Bitmap checkpoints
  • Text area checkpoints and output values
• Active Screen
• Navigate and Learn
• Customization of object identification properties in the Object Identification dialog box
• Tests and components recorded on a desktop browser
• Web file and frameset objects

Certain hybrid apps may issue an error "This test was created using an earlier version of UFT and therefore requires a different JavaScript engine".

This can happen if the app is launched by another app or from HOME.

Workaround: Have the app launched by the testing tool. Stop the recording, restart the app, but do not reinstall. Begin recording again. Alternatively you can use this Javascript code:

Additional limitations:

Working with non-packaged apps

Object description filter - example

Set oDesc = Description.Create()
	oDesc("class").Value = "Button"

Set Buttons = Device("Device").App("UICatalog_2").ChildObjects(oDesc)
               
NumberOfButtons = Labels.Count()

For i = 0 To NumberOfButtons - 1
	Buttons(i).Tap
Next	

Testing SAP Fiori apps with Digital Lab

If your test was created for a desktop version of a Fiori application, you may need to modify the test to ensure it runs correctly on the mobile version.

Additionally, different resolutions on different devices may cause differences in an object's properties and behavior. You may need to manually edit the test script to support multiple devices.

The following versions of the Microsoft Edge browser are supported:

• SAP Fiori: version 1.44 and 1.52 (Replay only)
• SAPUI5: version 1.44 (Replay only)

Specific SAP objects and methods

Standard checkpoints and output values in SAP Fiori apps

When inserting standard checkpoints and output values to an already recorded test, and running standard checkpoint and output value steps on Fiori mobile applications, the test object must be fully visible in the Digital Lab remote access window.

This is relevant when editing the test, and not when recording it.

Fiori 1.6x client freezes

The remote access display does not support apps using the Android FLAG_SECURE window flag. For details, see WindowManager.LayoutParams in the Android Developers documentation. To use such apps with Digital Lab you need to remove the flag. See the Digital Lab help for details.

Back to top

Unsupported features, test objects, and methods

The OpenText Functional Testing Mobile Add-in only supports recording and running steps on mobile applications.

When working with mobile objects, the following OpenText Functional Testing abilities are not supported, or are only partially supported:

• Active Screen.

• Assistive properties in the Object Identification dialog box.

• Device.SetOrientation method: Only the LandscapeRight and Portrait parameters are supported.

• Exist property for Mobile objects, when the object is not found, and the customer uses a default timeout value, or timeout value greater than 30 seconds (applicable to UFT 14.01 and earlier).

  Workaround: Add a timeout value of less than 30 seconds. For example:

  Device("Device").App("UICatalog").MobileList("list").Exist(3)

• Insight is supported only with image quality set to 100%.

  If you find that Insight does not work correctly even under these conditions, try using AI-based testing for your mobile application instead. See AI-based testing.

• LaunchBrowser. Although only the Browser argument is required, to prevent errors, you must define at least one other argument for this method. For details, see the LaunchBrowser documentation in the OpenText Functional Testing Help Center Object Model Reference.

• Local System Monitors. Instead, you can instruct OpenText Functional Testing to collect Mobile vitals in the Record and Run Settings dialog box. This data is then presented in the Local System Monitor pane in the run results.

• Low-level recording

• Maintenance Run Mode. Supported for hybrid applications only.

• To add a Set method to a MobileCalendar step (MobileStepper.Set), you must do so manually in the Editor.

• Tapping on a MobileStepper object (a MobileStepper.Tap method)

• Navigate and Learn, including adding children of a parent test object to the object repository.

• Recovery scenarios: The following trigger events and recovery operations are not supported for mobile:

  Trigger events	Popup window Object state Application crash
  Recovery operations	Keyboard or mouse operation > click button with label Close application process

• Simulation methods methods are not supported as the first step in a script, including the SetFingerprintSimulation, SimulteCamera, SimulateFingerprint, and SimulateVideo methods. To avoid errors, manually add a Launch step before any of these steps.

• Smart identification. Supported for hybrid applications only.

• Update Run Mode. Only the option for updating checkpoints and output values is supported. Supported for hybrid applications only.

• Virtual objects

• Visual Relations Identifiers (VRI) with multiple remote windows opened, or in Web tests on hybrid apps.

• WebVideo and WebAudio.Play

Back to top

Tests created in earlier versions of OpenText Functional Testing

• Tests created prior to UFT 12.51
• Tests created in UFT 12.02 Patch 1 or earlier
• Tests created with Mobile Center versions prior to 1.51

Tests created prior to UFT 12.51

For tests that were created on hybrid applications prior to UFT 12.51, only the text, isEnabled, and isFocused properties are supported for checkpoints and output values.

Additionally, you must make sure that OpenText Functional Testing re-installs or restarts the app before running steps on the app.

You can:

• Use the Record and Run Settings (for GUI tests).

• Add a step that uses the App.Launch method. For details, see the Mobile section of the Object Model Reference in the OpenText Functional Testing Help Center.

Tests created in UFT 12.02 Patch 1 or earlier

When working with an object repository in a test created in UFT 12.02 Patch 1 or earlier, the following commands are not supported:

• Highlight in Application

• Locate in Repository

Instead, update the test object descriptions from the application (select the test object and click Update from Application).

To update the description of a MobileLabel test object from the application, replace it with a MobileList test object.

In the relevant test steps, replace the steps containing MobileLabel.MakeVisible and MobileLabel.Tap with a single step containing MobileList.Select <index>.

For example, replace:

Device("Device").App("UICatalog").MobileLabel("ListViewActivity").MakeVisible
Device("Device").App("UICatalog").MobileLabel("ListViewActivity").Tap

with:

Device("Device").App("UICatalog").MobileList("list").Select 5

Tests created with Mobile Center versions prior to 1.51

If you have a test of containing steps on hybrid application which was created using Mobile Center versions prior to 1.51, this test is not supported on version 2.01 and later.

Back to top