Known Issues - Editing GUI tests

Relevant for: GUI tests and components

Spying

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

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

Canceling spying when in Hover mode is not supported.

Keep on Top

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

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

The following known issues exist when using the Object Identification Center:

Validate
  • Validate does not work properly when multiple SAPGUI objects match the description.

  • Validate is not supported on UIA Pro objects.

Hover mode

Objects spied in Hover mode cannot be added to object repositories or test editor with correct hierarchies and properties.

Workaround: Use normal mode of OIC or use the Object Spy.

When working in a non-English UFT One installation

Certain UI elements in the Object Identification Center pane are hard-coded in English and not translated.

The following known issues exist when using Object Spy or Object Identification Center:

AI Inspection / Highlight If a status bar exists at the bottom of Firebox browser, when you use AI Inspection or Highlight function in Object Spy or OIC, UFT One may be unable to get the correct positions of test objects.
Cannot spy by tapping UFT One supports spying on web-based applications only when using a mouse.

Back to top

AI Identification

AI Identification view

In some cases, when using AI identification to inspect a web application on Internet Explorer, UFT One sees the application as an empty black page.

Workaround: 

Wait until the web page is fully loaded and click REFRESH on the AI Identification view.

Dual monitors AI-based object identification is supported only on the primary monitor. Therefore, if you are using AI features when working with dual monitors, make sure that both the AI windows and your application are visible on the primary monitor.
This is relevant when inspecting applications, recording flows and running tests.

Back to top

Recording

Description properties UFT One 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 One 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 One cannot record or run steps if it has limited access to the processes of the application you are testing.

Workarounds:

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

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

Changes in the application during a recording session

When the title of a window changes during recording, UFT One 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.

Recording Insight objects

During an Insight recording session, if you perform an operation that moves the application window, an unexpected parent object is recorded. The parent object used in the step is the object located at the clicked location after the operation was performed.

Example: If you record a Minimize operation on a Calculator application, the Calculator closes and the step is recorded with the Desktop window as the parent:

Window("calculator").InsightObject("").Click
Window("calculator").InsightObject("").Click
Window("calculator").InsightObject("").Click
Window("Program Manager").InsightObject("").Click

Workaround: The recorded step still runs successfully if its image is unique within the parent object. Otherwise, you can manually move the object under the correct parent in the object repository and adjust the step.

Recording Insight objects on a remote Windows 10 machine

When you start an Insight recording session on a remote Windows 10 machine, your mouse cursor may jump around on the application screen.

Workaround:

  1. Launch gpedit.msc with administrative privileges.
  2. In the Local Group Policy Editor, navigate to the path below and set the Policy Use WDDW graphics display driver for Remote Desktop Connections to Disabled:

    Local Computer Policy -> Computer Configuration -> Administrative Templates -> Windows Components -> Remote Desktop Services -> Remote Desktop Session Host -> Remote Session Environment

Back to top

Actions

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 One'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 One to retrieve the object information from the application.

This may affect UFT One'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.

String to Integer

When a parameter is defined as Variant, the Keyword View sometimes inserts the value as a String.

To provide an Integer parameter, manually remove the quotes from the value after the step is created.

In some cases, this is mandatory, for example for the row parameter of DevExpress Data Grids.

For details on required parameter types, see the UFT One Object Model Reference for GUI Testing.

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

Checkpoints and output values

Accessibility checkpoints

In ALM, you can view a comparison of accessibility checkpoints in the Asset Comparison Tool only if both UFT One and the UFT One 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 One gathers information from the application under test. This can sometimes take up to two minutes.

File Content output values When creating File Content output values, using spaces in a Data table parameter names is not supported.
XML checkpoints
  • When running 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.

  • After running an XML checkpoint that validates the XML against an internally referenced schema, the step status and step description in the HTML report may report contradicting statuses. If either one reports a failure, this indicates that the checkpoint failed. For more details about the failure, view the test results in the Run Results Viewer.

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

Back to top

DPI scaling level

Using Windows scaling settings other than 100%, may cause UFT One to behave unexpectedly. For example, you may experience differences when spying, highlighting or recognizing objects.

To avoid errors, set the Windows settings to display all text and apps at 100%.

For example:

  • On Windows 7, browse to Control Panel\Appearance and Personalization\Display and select Smaller - 100% (default).
  • On Windows 10, browse to Control Panel\Appearance and Personalization\Display, and click set a custom scaling level. Then select 100% from the dropdown list.

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”)
    x 
  • Class methods. For example:

    class fooClass
    publicfunctionfoo
    sin(45)
    end function
    End Class
    Set x = New fooClass
    x

Back to top

Text test objects

Modifying test object descriptions

When you modify the test object image of a Text test object, UFT One uses OCR to extract the text from the image and updates the text property accordingly.

However, if you manually modify the text property's value, the test object image is not updated. The new value of the text property is used for object identification.

Multi-line text

Text test objects support only single-line text.

If, when learning a Text object, you select an image with multiple lines of text, a test object is created only for the first line.

Back to top