Known Issues- Web-Based Application Support

This section contains general troubleshooting and limitation information about UFT Web-based application support:

Test Objects, Methods, and Properties
  • Web test objects do not support the Class Name . If you try to run a ChildObjects(<Descr>) step on a Web object, and the Descr argument includes the Class Name property, a General Run Error message is displayed.

    Workaround: Use the micclass property in the Descr argument.

  • If you record drag and drop steps on a Web element within the same frame, the test steps may fail during the run session if the screen resolution is not identical to the screen resolution during the recording session. This is because the target location coordinates may be different for different screen resolutions.

    Workaround: If this problem occurs, adjust the Drop coordinates according to the new location.

  • UFT records changes in the edit field only on <input type="file"> tags. Browsing operations are not recorded.
  • Clicks on form tags of type POST may not run correctly.

    Workaround: If this problem occurs, change the replay type before the click to Run by mouse operations using: Setting.WebPackage("ReplayType") = 2. We recommend returning the replay type to the default (Run by Events) setting after the click step: Setting.WebPackage("ReplayType") = 1.

  • Defining xpath and css properties using Frame HTML tags is not supported. This may cause incorrect identification when identifying Frame objects or retrieving Frame objects using the ChildObjects method.
  • xpath and css properties are not supported for .NET Web Forms test objects or for other Web-based test objects that have .NET Web Forms parent test objects.
Creating and Running Testing Documents
  • For UFT to run JavaScript methods, the security settings in your browser must be set to allow active scripting. (In Internet Explorer, for example, you can find these security settings under: Tools > Internet Options > Security > Custom Level > Scripting > Active scripting.)

    This is relevant if your test steps include RunScript or EmbedScript methods, or if you are working with test objects supported using Web Add-in Extensibility, such as Web 2.0 test objects.

  • If you use the Tab key when recording password fields in the AutoComplete dialog box, UFT may record incorrectly.

    Workaround: Press ENTER after entering the user name or click the button for logging in.

  • When UFT opens a browser, it may not correctly recognize multiple tabs that were opened and saved from a previous browser session.

    Workaround: If multiple tabs are required, open them during the run session by adding the relevant steps to your test or business component.

  • When running in Maintenance Mode, UFT may replace test objects with XPath or css identifier property values with new objects from your application.

    Workaround: Use the Update from Application option in the Object Repository Manager to update specific test objects with XPath or css identifier property values.

Registering Browsers

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
  • Checkpoints on page source/HTML tags cannot be inserted from the Active Screen and must be inserted while recording. These checkpoints may fail during the first run session.

    Workaround: Perform an update run (Run > Update Run Mode) of your test or business component before you run a test or business component that includes a page source/HTML tag checkpoint.

  • If you insert checkpoints from the Active Screen when you are working with an application containing a browser control instead of a Web browser, your checkpoints may fail.

    Workaround: Insert checkpoints while recording.

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.

Problem

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.

Solution

Insert a Wait() statement before the first step on the second browser to enable the second browser to finish loading.

Reason

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:

  1. In Chrome, navigate to the address chrome://flags.

  2. In the Enable touch events option, set the option to Enabled.