This section contains general troubleshooting and limitation information about UFT Web-based application support.
|Class Name property||
Web test objects do not support the Class Name description property.
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.
|Recording drag/drop steps||
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.
|Edit fields||UFT records changes in the edit field only on <input type="file"> tags. Browsing operations are not recorded.|
|Form tags of type POST||
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.
|xpath and css description properties||
(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.
|Multiple browser tabs||
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.
|Data driving browser parameters||
If you are data driving your test using the Data Pane, and leave the Browser parameter value blank, UFT runs that iteration with the values defined in the Record and Run Settings dialog box.
For more details, see Desktop web testing parameter values.
UFT supports applications with embedded browsers only for applications that embed Internet Explorer.
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 on page source / HTML tags||
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.
|Applications with browser controls||
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.
|CSS values in multiple browsers||
When running tests, UFT retrieves CSS property values from the browser itself.
If your test must run on multiple browsers, keep in mind that different browsers may have different CSS functionality and return different property values for the same object.
|Browsers slow to load||
If a step intended to be run on a second browser runs before the second browser finishes loading, UFT will run the step on the first browser instead.
This may cause the step to fail. To prevent the steps from failing, insert a Wait() statement before the first step on the second browser to enable the second browser to finish loading.
|GWT Web apps||
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: