Known Issues - Google Chrome and Apple Safari

Functionality and Settings - Google Chrome / Apple Safari

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

Back to top

Test Objects, Methods and Properties - Google Chrome / Apple Safari

  • 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

    • about://* pages

    • Browser.Home method

    • Browser.FullScreen method

    • Browser.Object method

    • Browser.Stop

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

    • Dialog boxes opened by the browser, such as Alert, Confirmation, or Prompt messages on versions of Chrome earlier than 26.

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

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

Back to top

Google Chrome only

  • In the following cases, you must manually enable the Functional Testing Agent for Google Chrome extension:

  • Recording on Google Chrome is supported only from versions 31 and higher.

  • If you have a custom toolkit designed using Web Extensibility, UFT cannot handle some events on Chrome browsers.

  • If you have the Chrome developer tools currently open, UFT cannot spy on Web objects.

  • If you have a Chrome alert or warning dialog open, UFT cannot run or record tests or components on the browser.

    Workaround: Close the alert or warning dialog before trying to run or record a test or component.

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

  • When working with Chrome version 36 or earlier, UFT does not support Web test objects located inside iFrame controls with a blank or about:blank SRC description property value.

  • 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 recording on Google Chrome, UFT does not use the location to learn the object.

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

  • The Active Screen is not supported for use with Google Chrome browsers.

  • The Page/Frame options (Tools > Options > GUI Testing tab > Web > Page/Frame Options node) are not supported for recording in Google Chrome.

  • If the Record Coordinates option is selected in the Web > Advanced pane of the Options dialog box (Tools > Options > GUI Testing tab > Web > AdvancedRecord Settings section), UFT does not record correct coordinates on images in Google Chrome browsers.

    Workaround: Manually add the correct coordinates for the image after recording.

  • Frameset objects are not supported in Google Chrome browsers.

  • Using the Object Spy on Alert or Confirm dialogs in Google Chrome causes unexpected behavior in UFT.

  • When testing applications on Google Chrome in Windows 10, UFT does not record many user actions.

    Workaround: In Chrome, do the following:

    1. Navigate to the chrome://flags/ page.

    2. In the flags page, disable the Enable touch events option.

  • When accessing FTP servers using Google Chrome, UFT does not record actions on the server authentication dialogs.

  • Drag and drop methods

    When recording a test on a Web page coded in languages other than HTML5, drag and drop methods can be recorded in Internet Explorer only.

Back to top

Apple Safari only

  • Only Web test object steps can run on Safari. All other steps run locally on the UFT computer.

  • Recording steps on Safari is not supported.

  • Web 2.0 test objects or Web Add-in Extensibility-based test objects are not supported on Safari Browsers

  • UFT does not recognize internal Safari pages, such as the New Tab page.

  • The following functionalities are not supported when working with the Safari browser: 

    • Learning objects in the Object Repository Window or Object Repository Manager (you can learn objects using the Remote Object Spy)

    • Maintenance Mode

    • Highlighting an object from the object repository in the application

    • Creating an Active Screen or using the Update Run Mode to update the Active Screen

    • Checkpoints and output values that are not standard (such as File Content checkpoints and output values, Text checkpoints and output values, and Bitmap checkpoints).

      Note that Page checkpoints are supported, with the following limitations:

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

      • The value of the load time for Page and Frame test objects is always 0 when running on Safari. In Page checkpoints, the load time property is selected by default, therefore Page checkpoints may fail when running on Safari.

        Workaround: Deselect the load time property in Page checkpoints that need to run on Safari.

  • The following test objects and test object methods are not supported when running on Safari:

    • WebFile.Set method

    • Browser.ClearCache method

    • Browser.DeleteCookies method

    • Drag & Drop methods (on all Web test objects)

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

  • Depending on the performance of your connection to the Mac, statement completion for the Object property might not work.

  • During a run session, steps that click on a Web object that is supposed to open a new browser tab fail to open the new tab.

    Workaround: Disable the popup blocker in Safari. (Safari > Preferences > Security, clear the Block pop-up windows check box).

  • When running tests or components on Safari, recovery scenarios are not supported.

  • Running tests or components on Safari using the Mouse replay type is not supported.

    Make sure that Event is selected as the Replay type in the Run settings section of the Web > Advanced options pane (Tools > Options > GUI Testing tab > Web pane > Advanced node).

  • In the automation object model, WebLauncher.Browser does not support the Safari browser. To connect to a remote Mac during a test run and open the Safari browser, use the RemoteConnection utility object and its methods. For details, see the Utility Objects section of the UFT Object Model Reference for GUI Testing.

  • Performing Back or Forward options on Safari version 9 (El Capitan) causes unexpected behavior in UFT.

    Workaround: Do the following:

    1. In Safari. select Preferences > Advanced.

    2. In the menu bar, select the Show Develop menu in menu bar option.

    3. In the Develop menu, select Disable caches.

Back to top

See also: