Troubleshooting and Limitations - Google Chrome

Functionality and Settings

• Web pages that modify the browser's JavaScript functionality (for example, a Web page that replaces the JSON object) may cause UFT to behave unexpectedly.

• The font and color properties for link objects contain different values in different browsers. Therefore, if you create standard checkpoints in Microsoft Internet Explorer and select the font and color properties, running these checkpoints in Chrome or Safari may cause the checkpoints to fail.

• If you have multiple Chrome or Safari users defined, you must delete all users.

Test Objects, Methods and Properties

• When using Chrome or Safari, the innertext, outertext, innerhtml and outerhtml property values may differ from other browsers. Therefore, using these values in parameters or running checkpoints that use these property values may cause the steps to fail.

• The following test objects, methods, and other Web-specific functionalities are not supported in Chrome or Safari:

• ViewLink test object

• chrome://* pages

• Browser.Home method

• Browser.FullScreen method

• Browser.ClearCache method

• Browser.Object method

• Developer Tools pane. (Running steps on Chrome or Safari while the Developer Tools pane is open is supported.)

• Web pages that include frame sets.

• Web test objects located inside iFrame controls with a blank or about:blankSRC identification property value.

• WebXML test object (and, accordingly, XML checkpoints and output value steps).

• Web 2.0 test objects or Web Add-in Extensibility-based test objects.

• Web-based environments, such as Web-based SAP, Siebel, Java, .NET Web Forms, and so on.

Google Chrome

• If you are working in Google Chrome versions 25 or higher, you must enable the UFT Agent extension for Chrome manually.

• Internal Google Chrome pages, such as the about:blank page, Google Chrome sign-in page, Google Chrome Web Store, and Google Chrome's default tabs homepage are not recognized as Web pages but WinObjects.

• Recording steps in Google Chrome is not supported.

• Page checkpoints and bitmap checkpoints may fail when running on Google Chrome because of differences between Chrome and Internet Explorer. For page checkpoints this is related to differences in the handling of casing in HTML source files.

• Text checkpoints fail when running on Google Chrome.

• When spying on a Web file in Google Chrome, you get a fakepath for a Webfile value property.

• If you manually uninstall the UFT Agent extension from Chrome, you must manually reinstall it if you reinstall UFT.

Google Chrome Frame

• Any limitations described in the UFT product documentation for Google Chrome are also relevant for 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 and Browser Forward commands will not work when testing in Google Chrome Frame.

• You cannot run a test on multiple tabs using Google Chrome Frame.

• You cannot run a UFT test while running Google Chrome and Google Chrome Frame simultaneously.

• You cannot delete browser cookies.

• If your script navigates from one page to another in Google Chrome Frame, the next line in the script may take some time to execute.

• 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.

• UFT's Navigate and Learn functionality is not supported on Google Chrome Frame.