Known issues - Web Add-in

This topic 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

OpenText Functional Testing 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 OpenText Functional Testing 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.
When using dynamic add-in loading, objects are identified differently when you open the browser before or after you open the test.

Therefore, if you did not select the Web add-in when opening OpenText Functional Testing, make sure that you open the browser and test in the same order when learning the objects (spy/record) and when running the test.

Object identification

AI-based testing	When your browser scope is WebPage (the default), the drop-down items of a combo box are not properly visible to AI. As a result, the drop-down items are either not identified by AI, or are identified in the wrong location. Workaround: Change the browser scope mode to BrowserWindow using the step: `AIUTil.Context.SetBrowserScope BrowserWindow`
Using the Web and Siebel Add-ins together	If you open OpenText Functional Testing 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.
Browser popup dialog box	Try to avoid spying on browser popup dialog boxes, as this might cause OpenText Functional Testing to temporarily stop responding. If this does happen, close the dialog box manually. Tip: If a Windows message opens, with options to close the program of wait for it to respond, choose the Wait option.
Dynamically generated child WebTree objects	If the child items in a WebTree object are generated dynamically, the Select method might not be able to select the items in the tree. 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. These classes disable pointer-events, which are required for object recognition.

Browser zooming and Windows display scaling (DPI)

In some cases, to identify and highlight objects in the correct location, you must learn the objects and run the tests at 100% browser zoom level and Windows display scaling level.

In these cases	Set browser zoom level to 100%	Set Windows display scaling level to 100%
Working with Internet Explorer or IE mode in Edge
Working with Chromium Embedded Frameworks
Using the OpenText UFT Agent Chrome extension version 2022 available online or installed from the v3 folder. (How can I tell if I am using the relevant extension: Navigate to the chrome://extensions/ page and click Details on the OpenText UFT Agent extension. The Inspect views of the extension are service worker.)
Working on a Virtual Machine that is connected not by using Remote Desktop Connection

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

Running on cloud browsers

You can run tests on cloud browsers provided by OpenText Functional Testing Lab and view the application as the test runs. However, you cannot spy on applications or record steps. For details, see Test Web apps on cloud browsers.

Additional unsupported features

The following features are not supported when running tests on cloud browsers:

Business Process Testing
AI objects
Insight objects
Environment variables
Headless browsers
Automation scripts (automating OpenText Functional Testing)

Known issues

The following known issues are relevant when running web tests on cloud browsers:

Mouse replay types	Running tests on cloud browsers using the Mouse replay type is not supported. Make sure that Event is selected as the Replay type in the Run settings section of the Web > Advanced options pane (Tools > Options > GUI Testing tab > Web pane > Advanced node).
Running from Jenkins	When running from a Jenkins pipeline, browser parameters cannot be changed from the pipeline itself. Change the configuration directly in the test script. Jenkins Application Automation Tools plug-in versions 23.3 and 23.4: To run tests on cloud browsers, configure the connection to OpenText Functional Testing Lab in the Record and Run Settings dialog box, and leave the OpenText Functional Testing Lab connection settings empty in Jenkins.
Rerunning a test on a cloud browser	When you run a test on a local browser and re-run it on a cloud browser, the launched local browser tab is closed before running the test on the cloud browser. This occurs when Close the browser when the test closes is selected on the Web tab of the Record and Run Settings dialog.
Run on secure websites only	OpenText Functional Testing Lab cloud browsers support only https websites. Note: If you are working with Digital Lab version 23.4 and Edge or Firefox cloud browsers you need to include the https in the URL.
Running on sites that cannot be reached	If the URL you configure in your cloud browser cannot be reached, running a test step on the cloud browser will take a long time to respond.

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 version 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 OpenText Functional Testing with the AgGrid Add-in selected in addition to the Web Add-in. To open or run tests that were created in earlier 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 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 OpenText Functional Testing Object Model Reference.

WebUIGrid test objects

Starting from version 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 OpenText Functional Testing with the UIGrid Add-in selected in addition to the Web Add-in.

To open or run tests that were created in earlier 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.