Known issues

This section describes known issues when working with OpenText Functional Testing for Developers.

OpenText Functional Testing known issues are relevant as well. For details, see Known issues in the OpenText Functional Testing Help Center.

IDE Plugins

General

  • When using the Highlight option in the application model for a test object with VRI objects defined, the highlight operation succeeds only if exactly one object matches the description (including the VRI definitions). If multiple objects match, nothing is highlighted.

    Workaround: Use the VRI Preview option to check the description.

  • When working with Java 9, application model features in the IDE plugins are not supported.
Mac OS

When working on Mac, make sure that you open any IDEs supported by OpenText Functional Testing for Developers at least once before installing OpenText Functional Testing for Developers. Otherwise, the installation adversely affects the IDE's installation and you can no longer open the IDE.

To repair a damaged IDE installation, run the following command: 

xattr -d com.apple.quarantine <Path to IDE application>

Eclipse on Linux

  • To work with application models in Eclipse on Linux, you must start Eclipse as a root user.

  • IDE is not restored after closing the OIC or Test Recorder on Ubuntu.

    Description: When using Eclipse on Linux, the IDE does not automatically restore to its previous state after closing the OIC or Test Recorder. Users must manually restore the IDE.

    Workaround: Manually restore the IDE after closing the OIC or Test Recorder.
Eclipse 2021

An error occurs when working with application models in Eclipse 2021.

Cause: Incompatibility of some legacy OpenText Functional Testing for Developers files with the Java 16 JRE used in Eclipse.

Workaround: Add the following line to your eclipse.ini configuration file:

--illegal-access=permit
Eclipse-based IDEs

When working with the following environments, application model features are not supported:

  • Ubuntu with OpenJDK 9 or later

  • Fedora with OpenJDK 8 or later
Eclipse Kepler/Luna users

To use the Eclipse IDE for Java EE Developers or Eclipse Standard editions with the IDE plugin, you must deploy the Google Gson plugin to your Eclipse folder:

  1. Download the Google Gson plugin, version 2.1 or later, from the MVN Repository.

  2. Copy the downloaded .jar file to your <Eclipse deployment>\plugins folder and reopen Eclipse.
Visual Studio

Web-based AUTs

If your IDE is in front of your browser when you click the Highlight option from the Application Model editor or from the Object Identification Center, the Highlight rectangle appears, but sometimes the IDE window stays in focus and may block the object.

Workaround: Arrange your screen so that the IDE does not block your application.

IntelliJ IDEA

  • When moving an application model's .tsrx file to a different module/location while viewing it in the Editor's Design tab, the view changes to the Text tab.

  • IntelliJ suggests deleting some environment variables. Make sure not to delete the following variables: _JAVA_OPTIONS, JDK_JAVA_OPTIONS, and JAVA_TOOL_OPTIONS. These are installed by OpenText Functional Testing for Developers and are required for testing Java applications.

  • When creating or working with Application Models in IntelliJ IDEA 2022, you may encounter an error about user data not being supported.

    You can ignore this error, the functionality is not affected.
Changing the plugin installation on Linux or Mac

Use the Add/Remove Features option of the OpenText Functional Testing for Developers setup program to install or remove the IDE plugin from your IDEs.

If you make any changes to the plugin or IDE installation in other ways, keep the following in mind: 

The Add/Remove Features option assumes that the currently installed features are the ones last installed by the installer. If you made any manual changes in the plugin installation, the next time you use the Add/Remove Features option, you will not achieve the expected results.

For example, after manually removing the plugin, uninstalling the IDE, or moving it to another location, attempting to reinstall the plugin using the Add/Remove Features option does not install it. This is because the setup program assumes the plugin is still installed.

To fix this situation, first, run the installer as if to remove the plugins that are no longer there.

Then you can reinstall the plugin using the setup program's Add/Remove Features option.

Running tests

Running a test project with multiple classes

If you run multiple tests and each one performs a cleanup step, you may encounter warnings such as Class Cleanup method ImageTests.ClassCleanup failed. You can ignore this message, it just means that one test was trying to clean up something already cleaned up by a previous test.

Parallel test runs

  • Parallel test runs are not supported on Internet Explorer and Edge Legacy browsers.
  • The WebElement.dragAndDropOn method is not supported in parallel test runs.
  • If you run AI-based tests in parallel, we recommend not including AIRunSettings steps. Any settings you change affect all tests running in the same parallel run session, and may cause unexpected results.

Using a grid configuration

  • When running tests in grid mode, using VRI for object identification is supported only for web applications.

  • AGGrid and UIGrid objects are not supported when running tests on a Linux or Mac OpenText Functional Testing for Developers Grid node.

  • Nodes that connect to the same grid must have unique names. If multiple nodes with the same name connect to the grid, only the last node to connect will be available.

Test recorder

  • You cannot use the test recorder to record an action on a Web.FileField. Add this code manually to your test script.
  • The Browser.closeAllTabs action does not work as expected on Firefox during a test recording. Add this code manually to your test script.
  • You cannot use the test recorder to record test steps on applications in Safari.

Verifications

In some cases, a verification step on a multi-line text fails, though the expected and actual texts displayed in the report are identical.

Possible cause: The technology on which you are running the test requires a \r for line breaks.

Solution: Try adding a \r before each \n in the expected text in your step and try again.

Run result reports

  • When you specify the report's location in the ReportConfiguration object, the folder name can contain only utf-8 characters.

  • When working in Java based IDEs (IntelliJ, Eclipse, Android Studio), the Functional Testing for Developers > View Last Run Results is sometimes unexpectedly unavailable, or it opens the wrong project's report.

    Workaround: Open the HTML Report manually from your project's location in the file system.

PDF run result reports

  • To export run results to a PDF report, the run results folder must contain the runresults.json file. If you renamed this file for any reason, make sure to change the file name back before exporting the results to a PDF report.

  • If your run results include snapshots for each step, these are not exported to the PDF report.

  • When the run result descriptions are complex and include nested tables, some of the descriptions are not included in the PDF report.

  • You can export run results to a PDF report only on the same type of operating system that generated the results.

  • Some non-English characters are not supported, and are not displayed correctly in the generated PDF report.

Text recognition - OCR methods

  • Text recognition depends on font and image quality, as well as spacing and resolution. In some cases, text is not recognized as you would expect.

  • To use OCR methods, the ABBYY OCR engine has to be included in the installation.

  • Version 23.4 introduced some text recognition enhancements that might affect the behavior of tests written with previous versions:

    • An updated version of the ABBYY OCR engine is now used, enhancing its text recognition ability. Therefore, the results of the GetTextLocation or GetVisibleText methods are now more accurate.

    • AI-based text recognition now ignores text identified in unexpected areas or controls, and breaks up text strings based on the borders of identified UI controls. If your tests require restoring the previous behavior, contact support for assistance.

AI-based testing

  • When working on a computer that does not meet the AI installation requirements, some AI Object Detection features are still visible but are not supported. For requirements, see Installation prerequisites.

  • You can change AI settings during a run, using the AiRunSettings class in the SDK.

    Changes you make during the run affect all tests running in the same runtime session. These may be tests running in parallel or sequentially in the same runtime session.

  • The following AI Object operations are not supported on mobile applications: RightClick, DoubleClick, LongClick, SetText and Hover.

Technologies - general

  • When using the getSnapshot method, you can save the snapshot as a .png file only.

  • Some Windows updates delete registry keys required by OpenText Functional Testing for Developers and prevent it from working properly.

    Solution: After a Windows update, run a repair of the OpenText Functional Testing for Developers installation from the Control Panel.

  • On Windows 10, if you have only the German language pack installed, the Keyboard.sendString method sends some special characters incorrectly.

    Workaround: Install the English language package in addition to the German one.

Web technology

For known issues specific to web browsers, see Known issues - Web technology.

Java technology

For known issues specific to Java technology, see Known issues - Java technology.

.NET Windows Forms and WPF technologies

Windows Forms support

.NET 6 through 8 are supported as a Technical Preview.

Some objects supported in earlier .NET versions, such as PropertyGrid, ToolBar, Table, and StatusBar, will not be identified in these new versions.

To support these test objects, you can try using UIA Pro.

WPF ComboBox / WPF List test object

You cannot use the following to create the test object descriptions of WPF ComboBox or WPF List test objects:

  • C# properties: Items, SelectedItem, or SelectedItems
  • Java methods: getItems, getSelectedItem, getSelectedItems
WinForms Button test object

A WinForms Button test object cannot be identified if WindowId is the only property in its test object description.

WinForms Edit object

Before performing a Select operation on a WinFormsEdit object, you must first perform a Click operation on it.

Oracle technology

To recognize Oracle application objects, you must install and load both the Oracle Add-in and the Web Add-in.

Standard Windows technology

  • The ListViewItem.EnableLabelEditing method works only if it is preceded by an ActivateItem step.
  • In some cases, the application you are testing may have an integrity level higher than the test run. In such cases, run your test with Administrator privileges and/or open the runtime engine in Administrator mode.

SAPUI5 technology

  • When spying on an SAPUI5 list box, the Object Identification Center (OIC) displays the control type as Unknown.

  • AgGrid and UIGrid objects are not supported in CEF and Headless Chrome.

SAP GUI technology

The GuiSessionFactory.Attach method does not work as expected.

Terminal Emulator technology

  • The GetVisibleText()method from TestObjectBase does not work as expected for Terminal Emulator technology because of the third party library used for text recognition (OCR). This issue is known for other technologies as well.

  • SendKeys(Keys.ENTER) is not supported for TeTextScreen. To send the Enter key, use the Keyboard class. For details, see Send keystrokes to the AUT.

  • SetCursorPos and the properties current row and current column are not supported for TeTextScreen.

  • When highlighting Terminal Emulator test objects on IBM Host On-Demand or IBM i Access-Client Solutions, the highlighted location for some objects might be shifted.

    Workaround: Configure the text area and text screen settings in the Terminal Emulator Configuration Wizard. Run <Installdir>\bin\TeConfigWiz.exe to open the wizard, and then proceed to the Configure Emulator Screen Settings page. For details, see Configure Emulator Screen Settings Page, in the OpenText Functional Testing Help Center.

Testing mobile applications

General issues

  • When a property with an empty value is used in a test object description, the test object is not identified in the Object Identification Center, nor in the test during the test run.

  • Validate on iOS devices only works if the test object properties used for validation do not include MobileCenterIndex or Container.

  • When opening several tabs in a browser on a mobile device, only the first tab opened is recognized by the OpenText Functional Testing for Developers engine.

  • When running a Web test on a mobile device, if a modal dialog box displays on the browser, the test pauses and in the end times out without completing.

  • Mobile Center supports identifying an object by its parents only if the parent is part of the object description. This means that if the parent is not recommended as an identification property, you cannot add the parent property to help identify the object.

  • Radio button controls that are not defined as part of a radio button group are not supported.

  • Testing on the SAP Fiori native browser is currently not supported when parallel test running is enabled (default).

    Workaround: If you want to run tests on the SAP Fiori native browser, deactivate parallel testing on mobile devices.

    To deactivate parallel testing on mobile devices:

    1. In a text editor, open a new file.

    2. Copy and paste the following code: 

      {
  "labManager" : {
      "useLocalLabManager": true,
      "environments": ["web"],
   }
}
    3. Save the file as config.json in the <Installdir>\lwe\lightweight-engine\config\ folder.

User interface issues

  • On Windows, when selecting a device using the OpenText Functional Testing Lab dialog box, the device is not released when the dialog box is closed.

    Workaround: To release the device, you must manually restart the  runtime engine.

  • When connected to an iOS device, you cannot use the Object Identification Center to spy on a Mobile TabStrip object.

    Workaround: Create the object description or application model test object manually. See the SDK Reference for a list of available identification properties.

  • The Object Identification Center (spying objects) is not supported when emulating a device using Google Chrome's Device Mode.

  • When using the Object Identification Center to spy objects on Chrome or Safari browsers, if more than one tab is open on the browser, you can only spy the latest tab opened (the one on top).

  • When using the Object Identification Center for spying objects, unable to identify calendar and list in unpackaged applications.

Test object and method issues

  • Insight is not supported for the Application interface.

  • The Web.Frame object is not supported in Mobile browsers.

  • The following methods are not supported on iOS devices:

    Label.Tap() Stepper.Up()
    Label.LongPress() Stepper.Down()
    Pager.Set() TabStrip.Select()
    RadioGroup.Select() Table.Tap()
    Slider.SetPosition()

  • Device.SimulateIncomingSMS() and SimulateIncomingCall() are not supported.

  • Calling Mobile.EditField.getText for password fields, returns "encrypted text" instead of the actual value.