Support Matrix
OpenText Core Software Delivery Platform - Functional Testing Lab for Mobile and Web

Google

• Some Google Pixel devices do not support TalkBack audio accessibility testing.
• The model version combinations that have been identified as not supporting TalkBack accessibility testing are:
  • Android 13:Pixel 6a, Pixel 7 Pro
  • Android 13:Pixel 6 Pro, Pixel 6, Pixel 6a
• There may be additional unsupported model and version combinations, in particular versions running on Android 12

Samsung

• Minimum supported One UI version: One UI 2.5
• The following devices are supported:
• Samsung Galaxy Ax1: A11, A21, A21s, A31, A41, A51, A51 5G, A71, A71 5G
• Samsung Galaxy Ax2 : A02, A02s, A12, A22, A32, A32 5G, A42 5G, A52, A52 5G, A52s 5G, A72
• Samsung Galaxy Ax3 : A03, A03s, A13, A13 5G, A23, A23 5G, A33 5G, A53 5G, A73 5G
• Samsung Galaxy Ax4 : A04e, A04, A04s, A14, A14 5G, A34 5G, A54 5G
• Samsung Galaxy M: M56 5G
• Samsung S: S10, S10e, S10+,S10 5G ,S10 Lite, S20, S20+, S20 Ultra 5G,S20 FE, S21, S21+, S21 Ultra, S21 FE, S22, S22+, S22 Ultra, S23, S23+

Xiaomi and Redmi

• Xiaomi devices: Before using accessibility testing for the first time on a device, manually turn on or turn off TalkBack once to provide system permissions. If you reset the device to factory settings, perform this step again.
• Supported MIUI versions: 11 -14.
• Model number: China and Global models only.
• The following devices are supported:
• Mi 10: Mi 10, Mi 10 Pro, Mi 10T, Mi 10T Lite, Mi 10T Pro
• Mi 11: Mi 11, Mi 11 Pro, Mi 11 Ultra, Mi 11i, Mi 11 Lite 5G, Mi 11 Youth, Mi 11 Lite 4G
• Xiaomi 11: Xiaomi 11T, Xiaomi 11T Pro, Xiaomi 11 Lite 5G NE
• Xiaomi 12: Xiaomi 12, Xiaomi 12 Pro, Xiaomi 12X, Xiaomi 12T, Xiaomi 12T Pro, Xiaomi 12 Lite, Xiaomi 12S Ultra, Xiaomi 12S, Xiaomi 12S Pro
• Xiaomi 13: Xiaomi 13, Xiaomi 13 Pro, Xiaomi 13 Ultra, Xiaomi 13 Lite
• Note 7: Redmi Note 7, Redmi Note 7 Pro
• Note 8: Redmi Note 8, Redmi Note 8T, Redmi Note 8 Pro
• Note 9: Redmi Note 9, Redmi Note 9T, Redmi Note 9 Pro, Redmi Note 9S
• Note 10: Redmi Note 10, Redmi Note 10S, Redmi Note 10 Pro, Redmi Note 10 Lite
• Note 11: Redmi Note 11, Redmi Note 11S 5G, Redmi Note 11 Pro 5G, Redmi Note 11S, Redmi Note 11 4G, Redmi Note 11 Pro, Redmi Note 11 Pro+ 5G
• Note 12: Redmi Note 12, Redmi Note 12 Pro, Redmi Note 12 Pro+

Installation and upgrade

• A fully qualified domain name (FQDN) that starts with a number is not supported.

General

• Exploratory testing (iOS): A screenshot of the Start Record command is not recorded and not saved to the report log.
• iOS Agent signing API: Plug and play will fail if a device UDID exists in two different profiles, and one of these profiles has expired.
  Workaround: Delete the expired profile.
• Auto-dismiss system alerts: When the auto-dismiss system alerts when idle option is enabled on older iOS device models (devices released three years ago or more), there is a one minute delay before the alert is automatically dismissed. This is due to reduced performance on these devices as a result of running new iOS versions on old hardware.
• DexGuard/ ProGuard: Security tools which are used to protect apps against different risks, for example those of Guardsquare, may interfere with the OpenText Functional Testing Lab app packaging, as expected.
  To avoid such issues you can use the non-packaged app. If the packaged app is required, ask developers to provide builds for testing without the protection, or look for a workaround for the issue you encountered in the Troubleshooting section of the online help.
• In App interactions, when installing a different upload of an app with the same version and build number, comments are not displayed correctly on refresh.

Record and replay

• If your replay includes the installation of an app, the installation may fail if a system app pops up before or during replay.
• Recording of the Left and Right arrow keys within apps is not supported. The recorded Up and Down arrow keys are translated into a scroll during replay. In addition, when working with the OpenText Functional Testing Lab Browser, none of the arrows are recorded.
• Record and replay are only supported in the active browser tab. If you click back to a previous tab and perform actions, they will not be detected for record, replay, spy, or highlighting.
• Certain hybrid apps may issue an error "This test was created using an earlier version of Functional Testing and therefore requires a different Javascript engine". This can happen if the app is launched by another app.
  Workaround:Stop the recording, restart the app, but do not reinstall. Begin recording again.
• When recording a packaged hybrid app that is not designated as the Startup app, make sure that the hybrid app is included as one of the extra apps. This same guideline applies to the OpenText Functional Testing Lab Browser.
• When recording a complex web page through a non-packaged hybrid app or native browser, the first step may be not be recorded.
  Workaround: Wait several seconds and repeat the first step.
• Using packaged and non-packaged versions of the same app in the same test on a single device, is not supported.
  Workaround: Use different devices.
• Record and replay is not supported for Cocos2d-x frameworks apps.
• The Device.EnterKeys method is only supported when entering values from a physical keyboard, but not when values are entered on the soft keyboard from the device's remote access screen.
• When uploading apps specifying an icon in their xml file (instead of png): if the apps were obfuscated by DexGuard or other similar tools, the icon may not appear correctly in Functional Testing Lab for Mobile and Web.
• The Kill method is only supported for apps that exist on the Functional Testing Lab for Mobile and Web server.
• For the remote display to have the same orientation as the device, the initial orientation of the device must be set to portrait when starting a recording session.
• When working with fingerprint simulation, the Fingerprint Authentication dialog box may not trigger on certain Samsung Galaxy Note devices, due to the unique location of the touch sensor.
  To check if there is a touch sensor on your device, run the Android SDK's custom application call isHardwareDetected(). If a touch sensor is present, and the Fingerprint Authentication dialog box is not triggered, this indicates that the device is not supported. Instead, you will be prompted for a password.
• When using the installPackagedApp capability in Appium, the app may be launched twice when starting an Appium test. This does not interfere with the running of the test.

Record and Replay - Android specific

• For Android 8 and above, if secure layout is not supported, a white screen with message will be shown. For details, see WindowManager.LayoutParams.html. To use such apps with OpenText Functional Testing Lab you need to remove the flag. For details on how to remove the flag, see the online help.
• Photo and video simulation require that the application under test be able to access external storage. In certain devices, you need to manually enable this capability. To enable it, select the app in the Settings section, and under Permissions, select Enable storage.
• Record & replay of the Android app chooser system widget is not supported. An example is the selection of an email app when prompted by the device, if a default email app was not set.
• Working with the Multi-Window feature (also know as split-view) is not supported for Android.
• Spying on the suggestion list of the SearchView widget is not supported.
• The NumberPicker widget is supported only in native packaged apps.
• Some Android devices (such as certain Google Pixel or OnePlus devices) may not react to input from the PC keyboard.
  Workaround: Restart the mobile device.
• Android 10: Due to changes to the permissions model, when running apps that target Android 5.1 (API level 22) or lower on Android 10 for the first time, a permissions screen is displayed. This screen prevents OpenText Functional Testing Lab from successfully launching the app.
• Input method editor (IME) actions:
  • Functional Testing: To support IME actions on a text field in the device browser, the text field must still be in focus after entering several words or strings.
  • Appium: Running scripts containing IME actions on the device browser results in an error: "org.openqa.selenium.WebDriverException: An unknown server-side error occurred while processing the command. Original error: unknown error: performEditorAction is not defined."

Record and Replay - iOS specific

• Safari navigation is not supported on iPad OS 15 for hybrid non-packaged apps .
• For applications bigger than 50MB, there is a need to change the following configuration for a longer timeout - server\jetty\webapps\hp4m-connector\WEB-INF\classes\application.properties

  For Linux & Mac:
  

  connector.mac.ios10.timeWaitForInstall.in.millis=10000
  connector.mac.ios10.waitForInstall=true

  For Windows:
  

  connector.win.ios10.timeWaitForInstall.in.millis=5000

• Apps designed for iPhones are not supported by OpenText Functional Testing Lab when running in compatible mode on an iPad.
• Long browser scripts may fail to replay on the OpenText Functional Testing Lab Browser app.
• The Pinch gesture is ignored in replay with XCTest. The test will continue with replay, but the recorded Pinch gesture will be ignored.
• iOS 13:Functional Testing: Some sites are not supported for record and replay of hybrid non-packaged applications with the Safari web browser.

Packaged apps

• The MobileRadioGroup and MobileTabStrip objects support the selection of a radio button or tab only by index (not text).
• MobileSlider tap or swipes are rendered as SetProgress actions with the actual slider’s value.

Non-packaged apps

• Recording is only supported through the remote display.
• Replay of hybrid apps is not supported for multiple web views in a single session.
• Window.open is not supported for hybrid non-packaged apps.

Non-packaged apps - Android specific

• Toast notifications are not supported.
• Non-packaged apps built with Crosswalk projects framework are not supported.
• SAP hybrid non-packaged apps are not supported.
• Actions on date and time pickers are recorded as Tap actions and not as Set actions.
  Workaround: Manually modify the Tap actions to Set.
• For MobileList, Childobject only retrieves the child objects that are present on the screen.
• The MobileCalendar and MobileList objects are not recorded.
• When using the MobileRadioGroup object, you can select the object by index, but not by text.
• Steps that use a MobileObject with a View class will fail.
• MobileDropdown.select is not supported. Therefore, any test object method that uses an index for an argument value, is not supported for Android.
• Highlighting an object in the application on an Android device (which is based on an index of the specified object) may produce unexpected results. The MCindex will change from device to device or if the orientation changes, so in these cases highlighting might find another similar object (other properties of the object are the same, only the MCindex differs), or might not find the object. The look up mechanism uses the index only when the view provides no additional data (accessibility, resourceId, text, or hint).
• MobileEdit.setText will be recorded as an Enterkeys action.
• For testing tools: When a dialog box pops up in WebView, the JavaScript engine will pause until the dialog box is dismissed. As a result, when using non-packaged hybrid apps or the Chrome native browser, the fireEvent method will time out.
• When replaying a slide action on a SeekBar (such as your device’s brightness control), there may be a slight discrepancy between the actual value and the value used during replay. This discrepancy only exists on certain Android devices.
• Encrypted apps with a security framework are only supported in non-packaged mode.
• Replay on non-packaged hybrid apps does not support webview xss (cross-site scripting). Webviews loaded from local files within an non-packaged hybrid app, for example file:///android_asset/form.html, are not supported. The webview should be loaded from a web server and accessed through a URL.

Non-packaged apps - iOS specific

• Scroll to label in replay is only supported when the label is visible on the screen.
• Empty strings or NULL values are not supported for findElement. Make sure to specify a value such as a number, boolean, or string.
• Record and replay may fail for pages using dynamic URLs.
  Workaround: Begin recording the page again to get the right MobileWebView.
• Event simulation is not supported.

AWS server and Amazon Device Farm

• Device logs are not available for ADF devices.
• Amazon fire devices are not supported.
• Test duration on AWS is limited to 150 minutes. To extend this time, contact Amazon.
• You cannot set a reservation for an ADF device.
• For Functional Testing integration, you cannot run a test in which a single script uses multiple ADF devices. You can however, run iterations of a single test, using parameters to specify a different capability set for each iteration.
• If you chose a device based on capabilities, but did not specify an exact operating system, the device will not appear in the Functional Testing Lab for Mobile and Web console until after the device initialization is complete.
• The execution status of the test as displayed in Amazon does not match the actual functional execution status of the test. The execution status of the test should be monitored in Functional Testing test report.
• When viewing the Functional Testing Lab for Mobile and Web console located on an AWS machine, you may experience a delay in the refreshing of the data.
• On some applications, native alerts are not recognized.

Native browsers

• Only Chrome and Safari are supported as native browsers.
• Before recording or running tests, or spying/ highlighting objects, close all previously opened pages and tabs.
• Recording is not supported for auto-completed URLs. For example, if you begin typing a URL and an auto-complete drop-down list opens, your selection will not be recorded. On iOS devices, nothing will be recorded. On Android devices, it will record the previous selection.
  Workaround: Manually type in the whole URL or navigate via the drop-down list to the next page you want to test.
• Recording of popup windows is not supported for native or OpenText Functional Testing Lab browsers.
• Cross origin iframe sites are not supported for native browsers.
• The following test object methods are not supported:
  • Browser.CloseAllTabs
  • Browser.ClearCache
  • Browser.DeleteCookies
  • Browser.OpenNewTab
  • Browser.HandleDialog
• The GWT webtab, weblist, and webtree operations are not recorded on native browsers.

Native browsers - Android specific

• If you are using Chrome as a native browser, make sure that it is installed and set as the default browser. For devices that do not enable you to set a default browser, disable the system browser.
• For Android native browsers used with non-packaged hybrid apps: The WebSocket connection may fail, preventing the steps from being recorded by testing tools. Once you reinstate the WebSocket connection, the recorded steps, which were stored by the agent, will be added to the script.
• On the Chrome native browser, the following test object methods are only supported for replay:
  • Browser.Back
  • Browser.Forward
  • Browser.Refresh

Native browsers - iOS specific

• For certain iOS devices running iOS 13.0 or later (XCUITest), the device may disconnect from the Functional Testing Lab server when recording active dialog messages with the native browser.
• Setting the URL is not recorded on Safari and the OpenText Functional Testing Lab Browser app.
  Workaround: Update the script manually.
• iOS 13.0 and later: All open tabs must be closed before recording and replaying with the Safari browser.
• Replay is not supported when a page is opened in a new tab in the Safari browser.
• For iOS devices running in XCUITest mode, you may experience object recognition issues with hybrid apps and the native browser. To avoid these issues, make sure to follow Apple's UI design rules.