Known issues

This section describes known issues when working with UFT Developer.

UFT Developer inherits its capabilities from UFT and is affected by UFT's known issues as well. For details, see Known issues in the UFT Help Center.



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.

Eclipse Kepler/Luna users

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

  1. Download the Google Gson plugin, version 2.1 or later, from 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.

Back to top

UFT Developer Grid

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

Back to top

Parallel test execution

  • Parallel test execution is not supported on Internet Explorer and Edge browsers.
  • The WebElement.dragAndDropOn method is not supported in parallel test execution.

Back to top

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 actions on dialog or slider objects on Safari on Mac. Add this code manually to your test script.

Back to top

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.

Back to top

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.

Back to top

Technologies - general

  • When using the getSnapshot method, you can save the snapshot as a .png file only.
  • 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.

Back to top

Web technology

This section describes known issues when working with UFT Developer on various web browsers.


  • The FireEvent OnBlur event is not supported in Chrome.
  • If a Chrome browser is open and has an alert message box displayed prior to the start of a UFT Developer test run, you must manually close the message box before starting the run.
  • Using the Forward method when the current browser page is about:blank throws an exception and fails the test.

    Workaround: when on an about:blank page use the Navigate method instead of the Forward method.

  • Sometimes, after a browser page loads, operations on the page fail. For example a WebTable.SelectCell method may fail to select the cell.

    Possible cause: The site continues to load data after the page is loaded, and the operation performed requires an object that is not ready.

    Workaround: Instead of opening the browser using BrowserFactory, open the browser using a system process and attach it using BrowserFactory.

    For example: 

    new ProcessBuilder("C:\\Program Files (x86)\\Google\\Chrome\\Application\\chrome.exe","<MyURL>").start();
    Browser browser = BrowserFactory.attach(new BrowserDescription.Builder().title("<URL Title>").type(BrowserType.<TypeOfBrowser>).build());

Headless Chrome

  • If you run a UFT Developer test on Headless Chrome on a Mac, make sure that your test closes the browser by the end of the run. Otherwise, you will not be able to open Chrome again until you manually kill the Headless Chrome process.

  • SAPUI5-based applications are not supported on headless Chrome.

  • Menu, TabStrip, and TreeView objects are not supported.

  • Cross-domain iFrame objects are not supported.

  • The following operations are not supported:

    • Drag-and-drop operations

    • Browser Dialog operations: HandleDialog, HasDialog, GetDialogText

    • ImageUtils operations

    • Browser.ClearCache

    • BrowserFactory.GetAllOpenBrowsers

    • WebFile.Set()

    • VRI

  • BrowserFactory.Attach. You can attach only to the first tab for each browser. You cannot attach to a tab opened from the web page or by an Open New Tab command.

Internet Explorer

  • When using Internet Explorer 11 on a computer with UAC enabled:

    If a step in the test navigates from a protected-mode zone to a non-protected-mode zone, the navigation step succeeds, but any subsequent step will fail.

    Workaround: Reattach to the browser by calling BrowserFactory.Attach and then continuing with the browser that is returned.

  • When running tests in parallel on Internet Explorer 11, snapshots for controls received by the findChildren method do not appear in the run results report.
  • When recording on Internet Explorer on a computer with UAC enabled, whenever you navigate from a protected-mode zone to a non-protected-mode zone, an additional browser-launch step is recorded.


  • UFT Developer can work with Microsoft Edge browser only when launched with the Edge Agent for Functional Testing.
  • For UFT Developer to work with the Edge browser, UAC must be enabled.

  • UFT Developer has changed the way that the Microsoft WebDriver program (required for the Edge Agent for Functional Testing) is used. For details on the required steps to perform, see the Set up Microsoft Edge for UFT Developer (Windows only).

Multiple instances

You cannot open more than one instance of the Edge browser. This includes multiple BrowserFactory.Launch methods without closing the previous instances, or other methods that create a new browser instance such as Browser.OpenNewTab

Frame or iFrame objects

You cannot spy on or run steps on Frame or iFrame objects, or any elements inside these objects, using Microsoft Edge.

Unsupported methods

The following methods are not supported in Microsoft Edge:

  • FullScreen()

  • DeleteCookies()

  • File.SetValue()


Menu, TabStrip, and TreeView objects are not supported.

The following operations are not supported:

  • Drag-and-drop operations
  • Browser Dialog operations: HandleDialog, HasDialog, GetDialogText
  • WebFile.Set() operation
  • ImageUtils operations
  • VRI


Functionality and Settings

  • Web pages that modify the browser's JavaScript functionality (for example, a web page that replaces the JSON object) may cause UFT Developer to behave unexpectedly.

  • The font and color properties for link objects contain different values in different browsers.

  • If you have multiple Safari users defined, you must delete all users.

  • Safari does not work on Mac using a remote access window.

Test Objects, Methods and Properties

  • When using Safari, the innertext, outertext, innerhtml and outerhtml property values may differ from other browsers. Therefore, using these values in parameters may cause the steps to fail.

  • The following test objects, methods, and other Web-specific functionalities are not supported in Safari:

    • ViewLink test object

    • about://* pages

    • Browser.Home method

    • Browser.FullScreen method

    • Browser.Object method

    • Modal or modaless dialog boxes
    • Developer Tools pane. (Running steps or Safari while the Developer Tools pane is open is supported.)
    • Dialog boxes opened by the browser, such as Alert, Confirmation, or Prompt messages.

    • WebXML test object (and, accordingly, XML checkpoints and output value steps).

    • Web-based environments, such as Web-based SAP, Siebel, Java, .NET Web Forms, and so on.


  • Web 2.0 test objects or Web Add-in Extensibility-based test objects are not supported on Safari

  • UFT Developer does not recognize internal Safari pages, such as the New Tab page.

  • The following test objects and test object methods are not supported when running on Safari:

    • WebFile.Set method

    • Browser.ClearCache method

    • Browser.DeleteCookies method

    • Drag & Drop methods (on all Web test objects)

    • Web test objects located inside iFrame controls with a blank or about:blank SRC value.

  • During a run session, steps that click on a Web object that is supposed to open a new browser tab fail to open the new tab.

    Workaround: Disable the popup blocker in Safari. (Safari > Preferences > Security, clear the Block pop-up windows check box).

  • Performing Back or Forward options on Safari version 9 causes unexpected behavior in UFT Developer.

    Workaround: Do the following:

    1. In Safari. select Preferences > Advanced.

    2. In the menu bar, select the Show Develop menu in menu bar option.

    3. In the Develop menu, select Disable caches.

  • In certain configurations, the Object Identification Center and test runs do not work properly on the first browser tab that is opened.

    Workaround: Select the Auto Proxy Discovery protocol in your network settings:

Attributes property (C#) or getAttributes property (Java)

In some cases, the Attributes collection returned by Attributes property (C#) or getAttributes (Java) may be different between Internet Explorer and other browsers such as Chrome or Firefox.

Navigating to a new page

If you perform a step that navigates to a new page immediately followed by an image capture operation such as OCR operations, image verifications or comparisons (VerifyImageMatch, VerifyImageExists, CompareImage, LocateImage) or the GetSnapshot method, the step may fail.

Workaround: Add a browser.Sync() step before your image capture operation.


If the SAPUI5 add-in is loaded (selected in Settings > Engine tab ), UFT Developer cannot recognize Web TreeView, Menu, or TabStrip test object types.

Back to top

Java technology

Working with JavaFX in Java 11

To use UFT Developer with JavaFX applications in Java 11, perform the following steps on the computer running your application:

  1. Download the JavaFX module and store it locally.

    Caution: Make sure the path to the JavaFX module does not contain any spaces.

  2. Set the following environment variables.

    • PATH_TO_FX = <JavaFX module location>\lib.

    • In PATH, add %PATH_TO_FX%.

    • JDK_JAVA_OPTIONS = --module-path %PATH_TO_FX% --add-modules=javafx.controls,javafx.fxml,javafx.base,javafx.swing, --add-opens --add-opens javafx.base/com.sun.javafx.event=ALL-UNNAMED --add-opens --add-opens --add-opens javafx.base/javafx.event=ALL-UNNAMED --add-opens --add-opens

Working with JavaFX in Java 12

To use UFT Developer with JavaFX applications in Java 12, perform the following steps on the computer running your application:

  1. Download the JavaFX module and store it locally.

    Caution: Make sure the path to the JavaFX module does not contain any spaces.

  2. Set the following environment variables.

    • PATH_TO_FX = <JavaFX module location>\lib.

    • In PATH, add %PATH_TO_FX%.

  3. We recommend not running a command line window and your application at the same time. Therefore, launch the application from a batch file instead of using a command line that specifies the module path and dependencies:

    In the folder containing your application's .jar file, create a .bat file containing the following command: 

    start javaw --module-path="%PATH_TO_FX%" --add-modules={all modules required by your application} --add-opens {specify opens for modules if required} -jar <Application_Name>.jar


    start javaw --module-path="%PATH_TO_FX%" --add-modules=javafx.controls,javafx.fxml,javafx.base,javafx.swing, --add-opens --add-opens javafx.base/com.sun.javafx.event=ALL-UNNAMED --add-opens --add-opens --add-opens javafx.base/javafx.event=ALL-UNNAMED --add-opens --add-opens -jar JavaFX.jar

    Save the .bat file and run it.

Installing Java on a Windows machine with UFT Developer

When re-installing or upgrading the JRE on a Windows machine with UFT Developer installed, you might encounter error 1603 preventing the JRE installation to complete.

This can be caused by an interference between the UFT Developer Java environment variables and the Java installer.

To successfully complete the installation, rename the UFT Developer Java environment variables, perform the JRE installation and restore the variable names.

To temporarily rename the UFT Developer Java environment variables: 

  1. On your Windows Desktop, right-click My Computer or This PC and select Properties.

  2. Select the Advanced tab.

  3. Click the Environment Variables... button.

  4. Look for the following environment variables both under the user variable list and the system variables list and edit their names:


    • Java_Tool_Options

    • IBM_Java_Options

  5. Install the JRE.

  6. Once the installation is completed, change the environment variables names back to their original names.

Back to top

.NET Windows Forms and WPF technologies

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

UFT Developer cannot identify a WinForms Button test object 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.

Back to top

Oracle technology

For UFT Developer to recognize Oracle application objects, you must install and load both the Oracle Add-in and the Web Add-in.

Back to top

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 UFT Developer test run. In such cases, run your test with Administrator privileges or open the UFT Developer runtime engine in Administrator mode.

Back to top

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.

Back to top

Terminal Emulator technology

  • The GetVisibleText()method from TestObjectBase does not work as expected for Terminal Emulator technology because of the third party library for text recognition (OCR) used by UFT Developer. 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.

Back to top


When working with Java 9 on Mac versions Sierra or later, the UFT Developer tray icon is not displayed. To start and stop the UFT Developer runtime engine and to open the Settings dialog box, use command line scripts as described in the relevant topics. For details, see Customize UFT Developer runtime engine settings and Start/Stop the runtime engine.

Back to top


  • Testing mobile apps with UFT Developer. For notes and limitations related to testing mobile apps with UFT Developer, see the UFT Mobile Help.

  • Service Virtualization (UFT Developer 15.0.1 or later): When using SV during UFT Developer test design on Linux or Mac, the SV user interface sometimes appears to flicker.

Back to top