Troubleshooting and Limitations – Internet Explorer

General troubleshooting and limitation information about Internet Explorer when working with Unified Functional Testing (UFT)

Test Objects, Methods, and Properties

  • Recognition of test objects when using AutoXPath is very slow for web pages in Quirks Mode and Almost Standards Mode.
    Workaround: Convert the web page into Standards Mode by adding or changing the DOCTYPE of the page into <!DOCTYPE.htlm> or <!DOCTYPE.HTML PUBLIC "-//W3C//DTD HTML 4.01//EN""" or disable AutoXPath capabilities in UFT by clearing the Learn and run using automatic XPath identifiers in the Web > Advanced pane (Tools > Options > GUI Testing tab > Web > Advanced node).
  • When using the RunScript method with protected mode ON, Alert, Confirm, or Prompt dialogs are not displayed.
    Workaround: When writing a RunScript method, use the following method syntax: Set wnd=Browser("<browser name>").
    Page("<page name>").RunScript("window") wnd.alert()’ or Browser("<browser name>").Page("<page name>").RunScript "setTimeout(function () {alert(); }, 0)".


When recording a test on Internet Explorer 8 or earlier with the Active Screen enabled, performance on the site may become very slow. This is due to a performance issue in the JavaScript engine used in these browsers.
Workaround: Record the test using Internet Explorer 9, or disable the Active Screen. For details, see the HP Unified Functional Testing User Guide.

Web 2.0 Support

Due to synchronization issues, if navigating to a new Web page in Internet Explorer while recording, then UFT may not record certain operations on certain ASP .NET Ajax or jQuery UI objects in the page. Similarly, when running steps that navigate to a new page, UFT may fail to perform certain steps on certain ASP .NET Ajax or jQuery UI objects.

Workaround: If the problem occurs while recording, refresh the Web page and record the step again. If the problem occurs while running, insert a Wait() statement before the problematic step.

Internet Explorer 9

  • The WebXML object is not supported on Internet Explorer 9 in standard mode.
  • XML checkpoints are not supported on Internet Explorer 9 in standard mode.

Google Chrome Frame

  • Google Chrome Frame is used for only one page at a time, and does not have access to Internet Explorer’s browsing history. For this reason, the Browser Back (CMD_BROWSER_BACK) and Browser Forward (CMD_BROWSER_FORWARD) commands will not work when testing in Google Chrome Frame.
  • It cannot be run a test on multiple tabs using Google Chrome Frame.
  • It cannot be run a UFT test while running Google Chrome and Google Chrome Frame simultaneously.
  • The OpenTitle and OpenURL Browser object identification properties may return incorrect values. This is because Google Chrome Frame creates a new Browser object for each navigation activity.

Leave a Comment