Known issues

Backward Compatibility

The following changes may be required to tests that were created in previous versions of LeanFT

Back to top



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 LeanFT 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

Parallel test execution

If several instances of the same JavaScript Web test are running in parallel, LeanFT fails to replay the WebElement.dragAndDropOn method.

Back to top

Object identification center (OIC)

In the LeanFT OIC for Linux/Mac, the rows property is not displayed for a web table.

Back to top

Technologies - general

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

Back to top

Web technology

  • 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 LeanFT 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.

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

    If a step in the test navigates from a permitted zone to a non-permitted 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.

LeanFT can work with Microsoft Edge browser only when launched with the Edge Agent for Functional Testing.

LeanFT 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 LeanFT (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()

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 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.

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

  • LeanFT 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 LeanFT.

    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.

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.

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

Back to top

.NET Windows Forms and WPF technologies

WPF ComboBox / WPF List test objects

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 objects

LeanFT cannot identify a WinForms Button test object if WindowId is the only property in its test object description.

WinForms Edit objects

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

Back to top

Standard Windows technology

The ListViewItem.EnableLabelEditing method works only if it is preceded by an ActivateItem step.

Back to top

SAPUI5 technology

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

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 LeanFT. 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.


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

  • UFT API Tests. UFT API tests that are parametrized from excel files cannot be called and run from LeanFT tests (C# and Java).

Back to top