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.
-
When using dynamic add-in loading, UFT One identifies objects 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 UFT One, 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
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:
|
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 |
|
Rows/columns |
|
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.
See also:
- Known Issues- Web-Based Application Support
- Known Issues - Embedded frameworks and headless browsers
- Known Issues - Internet Explorer
- Known Issues - Microsoft Edge Legacy
- Known Issues - Google Chrome, Microsoft Edge (Chromium-based), and Mozilla Firefox
- Known Issues - Apple Safari
- Known Issues - Web 2.0 Add-ins