Known Issues - Editing GUI tests

Relevant for: GUI tests and components


The following known issues exist when using the Object Spy Hover mode:

  • The Object Spy's Compare functionality disables Hover mode. This means that if you spy using Hover mode, and then click Compare, you must spy on your second object by clicking.

  • Canceling spying when in Hover mode is not supported.

  • Keep on Top is not supported for the Object Spy in Hover mode.

  • Logical name definition, defined in the Object Identification Dialog Box, is not used when spying in hover mode.

Back to top


Description properties UFT does not record the visual relation identifier property.

This property can be added only manually from the Object Properties dialog box or the Object Repository Manager or window.

Start menu/ Quick Launch panel
  • Windows 7 / Windows Server 2008 R2: You must restart your computer after installing in order to record on the Start menu or Quick Launch panel.

  • UFT does not record launching Windows Help from the Start menu.

  • To record Start menu items customized as menus, customize them as links instead, or record their activation in some other way.

Dragging the Record toolbar

By default, dragging the Record toolbar to the top of the screen in Windows 7 or Windows 8.x or higher is not allowed.

To allow this, in the Windows Control Panel, select Ease of Access > Ease of Access Center Make the mouse easier to use, and disable the Prevent windows from being automatically arranged when moved to the edge of the screen option.

Limited access to application objects UFT cannot record or run steps if it has limited access to the processes of the application you are testing.


  • Make sure that the application you are testing is started by the same Windows user as UFT.

  • Make sure that neither you nor the tested application actively prevent UFT from accessing the application's processes.

Changes in the application during a recording session

When the title of a window changes during recording, UFT may fail to recognize objects within that window while running the test or component.

Workaround: Remove the text property from the window's test object description in the Object Repository window.

Back to top


Test names in actions

If a test contains a call to an action stored in another test, and that other test was renamed in ALM, the original test name still appears (in square brackets) in the canvas.

The obsolete name in the canvas does not affect UFT's ability to locate and run the action.

If it is important to display the correct test name, delete the action call from the test and reinsert it.

Nested actions

You cannot add a new action as a nested action to an external action.

Instead, open the external action and add the call to the nested action directly.

Copies of tests

If you make a copy of an existing test, you cannot insert call to parallel actions in both tests from the same test.

Instead of copying the test, use Save As to create a duplicate of the test.

Back to top

Keyword View

Object properties

If you use the Object property in a step in the Keyword View, it may take a long time for UFT to retrieve the object information from the application.

This may affect UFT's response time when you open and select from the various drop-down lists in the step.

If this occurs, use the Editor when working with the Object property.

Calls to other actions

If you insert a call to another action, you cannot expand the action node to view the steps in the called action.

Instead, double-click the called action node to open the action steps in another tab.

Back to top

Recovery scenarios

If you specify multiple function libraries from different locations with the same name in the same recovery scenario, only the first function library is used.

Workaround: Rename the function libraries so that each function library has a unique name.

Back to top

Object repositories

  • If you modify the name of a test object in the Object Repository while your test or component script contains a syntax error, the new name is not updated correctly within your test or component steps.

    Workaround: Clear the Automatically update test and component steps when you rename test objects check box (Tools > Options > GUI Testing tab > General node) and perform the renames in the steps manually (recommended) or solve the syntax error, and then close and reopen the document in UFT to display the renamed objects in your steps.

  • For actions: If you use the Export and Replace Local Objects option for an object repository that contains action parameters, the created repository parameters are mapped to test parameters instead of action parameters.

    Workaround: Manually adjust the mapping in the exported object repository.

  • You can add a test object to the local object repository only if that test object does not already exist in a shared object repository that is associated with the action or component. If a test object already exists in an associated shared object repository, you can add it to the local object repository using the Copy to Local option. For details, see Local copies of objects in shared object repositories .

  • You cannot add WinMenu objects directly to an object repository using the Add Objects to Local button in the Object Repository window or the Add Objects button in the Object Repository Manager. If you want to add a WinMenu object to the object repository, you can use the Add Objects or Add Objects to Local button to add its parent object and then select to add the parent object together with its descendants, or you can record a step on a WinMenu object and then delete the recorded step.

Back to top


Accessibility checkpoints

In ALM, you can view a comparison of accessibility checkpoints in the Asset Comparison Tool only if both UFT and the UFT Add-in for ALM are installed on the ALM computer.

Bitmap checkpoints

Bitmap checkpoints on objects containing text may fail if you create them using a Remote Desktop Connection and then run them locally, or if you create them locally and then run the checkpoint steps using a Remote Desktop Connection. In the run results, the image displayed when you click View Difference in the bitmap checkpoint results shows some text shapes.

Workaround: Enable the Font smoothing option in the Remote Desktop Connection application.

Database checkpoints
  • The format of captured values varies depending on the specific system settings. For example, date and time values may be set to different formats.

    Workaround: If you are running the test or scripted component on a different system than the one you used to record the test, confirm that the systems use the same format settings.

  • When you create a database checkpoint on one machine and try to run it on different machine, you should have the same ODBC driver installed on both machines.
  • In the Database Query Wizard, you cannot select Microsoft Query to create database checkpoints or output values if Power Query is installed on your computer. Instead, select the Specify SQL statement manually option.
File content checkpoints
  • File content checkpoints for htm/html files generated dynamically by third-party Javascript code are not supported.

  • When creating File Content checkpoints, UFT gathers information from the application under test. This can sometimes take up to two minutes.

XML checkpoints
  • When executing an XML checkpoint on an XML file that contains > as a value, an error message may occur.

  • When you add a new value node to an XML node, in some cases the new value may not be displayed.

    Workaround: Close the Edit XML as Text dialog box and reopen it to display the new value node correctly.

  • When inserting an XML file checkpoint on a file that cannot be loaded, or a file that is formatted incorrectly, you may receive an error message.

  • Creating and running XML checkpoints for large XML documents may take a few minutes.

Working with ALM In ALM, you cannot create, edit, or rename checkpoints for keyword GUI components.

Back to top

Using statement completion

Statement completion is not available for the following types of code:

  • Variables. For example:

    Set x = CreateObject(“Application.Excel”)
  • Class methods. For example:

    class fooClass
    end function
    End Class
    Set x = New fooClass

Back to top