Known issues - Web Add-in

This section contains general troubleshooting and limitation information about working with the Web Add-in.

Note: Some folder paths intentionally include previous company branding, due to backward compatibility considerations.

General

UFT One web agents on different pages and frames use window.postMessage to communicate with each other. If the application you are testing listens to MessageEvent, and handles messages from the UFT One web agent, unpredictable behavior may occur.

It is generally recommended that web applications be designed to ignore messages from sources other than itself. For details, see https://developer.mozilla.org/en-US/docs/Web/API/Window/postMessage#Security_concerns.
Regular expressions are not supported for numeric properties of Web test objects, such as WebButton.

Object Identification

Zooming in or out on a web page	UFT One 15.0.1 and earlier, or when using Internet Explorer or Safari, or working with JavaFX controls: Zooming in or out on your web page, may cause UFT One to behave unexpectedly when highlighting or recognizing objects. Keep your browser at the default zoom level. See also DPI scaling level.
Using the Web and Siebel Add-ins together	If you open UFT One with the Siebel Add-in loaded, the Web Add-in does not appear in the Object Identification dialog box. Workaround: Change the value of the HKEY_CURRENT_USER\Software\Mercury Interactive\QuickTest Professional\MicTest\Packages\SiebelPackage\Settings\AllowWebToConfig registry key value to 1.
Empty values returned	If your application objects do not implement the aria-selected attribute in the application's controls, certain description properties return empty values. Affected properties include: selected, items count, selected items, selection, and value return empty values.
Dynamically generated child WebTree objects	If the child items in a WebTree object are generated dynamically, UFT One may not be able to select the items in the tree automatically using the .Select method. Specifically, this may occur when the child objects are not visible or present in the application until the parent node is expanded. Workaround: Manually add steps to make the nodes visible or expand tree nodes to create the object in the application.
Bootstrap libraries	Objects in a BootStrap library that use the <a> element with both the btn and disabled classes cannot be recognized by UFT One. These classes disable pointer-events, which are required for UFT One object recognition.

Recording

Autocomplete during recording sessions

Autocomplete is not supported during recording sessions. When recording on an autocomplete control, enter the full string instead of selecting the suggestion provided by the control. The step is recorded in the same way as other (non-autocomplete) controls.

Workaround: You can disable the AutoComplete feature in Microsoft Internet Explorer by selecting Tools > Internet Options > Advanced and deselecting the Use inline AutoComplete under the Browsing options.

Recording WebTree objects with child objects

If a WebTree object contains separate objects inside the tree (such as a checkbox object), these child objects are not recorded.

Workaround: Do one of the following:

Spy on the child object

Do the following:

Spy on the child object to get the relative Xpath value of the tree item.
Then, add a WebTree.Select method, with the Xpath value you retrieved from the spy for the XPath argument of the .Select method.

Add the object manually

Add the object into the object repository and manually add it to the test or component.

Recording objects embedded in Web tables

If you are recording actions on objects embedded in a Web table, these actions may not be recorded properly. Readjust your test after recording as necessary.

Checkpoints

Bitmap and page checkpoints created on one browser may fail when running on another browser, because different browsers visually render web objects differently.

For page checkpoints this is related to differences in the handling of casing in HTML source files.

WebAgGrid test objects

Related Add-ins	Starting from UFT One 15.0, WebAgGrid objects are supported by the AgGrid Web child Add-in, which is not loaded by default. If you want to test AgGrid objects, make sure to open UFT One with the AgGrid Add-in selected in addition to the Web Add-in. To open or run tests that were created in earlier UFT One versions and use AgGrid objects, associate the AgGrid Add-in with the tests in the Properties pane of their Test Settings.
Checkpoints	Checkpoints on WebAgGrid test objects only validate table content that is available in the DOM. Checkpoints may fail because of the UFT is debugging banner displayed in Chrome while running a test. Close this banner and re-run your test. To close the banner, do one of the following: Close the banner manually when running the test. Enable silent debugging in Chrome settings.
Rows/columns	Operations of collapsed rows or columns may behave unexpectedly. To avoid errors, ensure the row or column is expanded before running your test. Operations on a row or a column with a large number may behave unexpectedly.
WebAgGrid.GetCellData	If a WebAgGrid object is sorted by column, the column cannot be identified by the GetCellData method. Note: GetCellData steps will fail only for the sorted column. All other columns are identified successfully. Workaround: Remove sorting on the column and run your test again.
Specifying a property to use for an object's logical name	Logical name definition is not supported for WebAgGrid and WebUIGrid test objects.

For more details, see the WebAgGrid object in the UFT Object Model Reference.

WebUIGrid test objects

Starting from UFT One 15.0, WebUIGrid objects are supported by the UIGrid Web child Add-in, which is not loaded by default. If you want to test UIGrid objects, make sure to open UFT One with the UIGrid Add-in selected in addition to the Web Add-in.

To open or run tests that were created in earlier UFT One versions and use UIGrid objects, associate the UIGrid Add-in with the tests in the Properties pane of their Test Settings.
Checkpoints on WebUIGrid test objects only validate table content that is available in the DOM.
Logical name definition is not supported for WebAgGrid and WebUIGrid test objects.