This section contains general troubleshooting and limitation information about UFT Web-based application support:
|Test Objects, Methods, and Properties||
|Creating and Running Testing Documents||
UFT supports applications with embedded browsers only for applications that embed Internet Explorer.
|Recording||When recording on certain types of applications on Internet Explorer, for example Oracle ADF applications or applications built with Smart GWT, UFT can experience unexpected results.|
|Checkpoints, Output Values, and the Active Screen||
|Working with Multiple Web Browsers||
UFT retrieves the CSS property values from the browser. When designing tests or components that will run on different browsers, keep in mind that different browsers may have different CSS functionality and return different property values for the same object.
When running steps that are intended to be performed on different browsers, and UFT tries to perform the step intended for the second browser before the second browser has finished loading, UFT will perform the step on the first browser, and the step may fail.
Insert a Wait() statement before the first step on the second browser to enable the second browser to finish loading.
By default, a Browser test object does not have any description properties in its description. When only one browser is open, the open browser matches the (empty) description for any Browser test objects. When multiple browsers are open, UFT uses smart identification or the ordinal identifier property value stored with the relevant Browser test object to distinguish between the browsers and to select the correct browser.
However, if a second browser has not fully loaded when UFT tries to perform a step intended for that browser, UFT will assume that only one browser is open and it will try to perform the step on the first browser without reverting to smart identification or ordinal identifiers.
|Web Accessibility Toolkit||
When recording on a Web applications created with Google Web Tools (GWT) using the Chrome emulator browser, the application can experience unexpected behavior, including becoming non-responsive to your actions.
Workaround: Enable touch events in Chrome: