For example, this would include a Web page that replaces the JSON object.
|Link fonts and colors||
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.
|Chrome / Safari users||
If you have multiple Chrome or Safari users defined, you must delete all users.
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:
|Chrome alerts or dialog boxes||
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||
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.
|Manually enable the extension||
You must manually enable the Functional Testing Agent for Google Chrome extension in the following cases:
For more details, see Enable the Functional Testing Agent Chrome extension.
|Manually removing the extension||
If you manually uninstall the UFT Agent extension from Chrome, you must manually reinstall it if you reinstall UFT.
If you have a custom toolkit designed using Web Extensibility, UFT cannot handle some events on Chrome browsers.
When testing applications on Google Chrome in Windows 10, UFT does not record many user actions.
Workaround: In Chrome, do the following:
Unsupported UFT functionality in Safari
The following functionalities are not supported when working with the Safari browser:
Recording. Recording steps on Safari is not supported.
Highlighting and learning:
Highlighting an object from the object repository in the application is not supported.
Learning objects in the Object Repository Window or Object Repository Manager is not supported. Instead, learn objects using the Remote Object Spy.
Maintenance Mode is not supported for Safari.
Active Screen. Creating an Active Screen or using the Update Run Mode to update the Active Screen is not supported in Safari.
Non-standard checkpoints and output values are not supported. This includes File Content checkpoints and output values, Text checkpoints and output values, and Bitmap checkpoints.
Page checkpoints, however, are supported. For details, see Page checkpoints.
UFT does not recognize internal Safari pages, such as the New Tab page.
Safari caching issues: When your script performs an operation, goes back to the previous page, and then attempts to recognize a link object, UFT cannot recognize the link object on Safari versions 11 and higher.
This is caused by Safari's caching functionality. For more details, see the Apple developer forum.
Workaround: Refresh the page before trying to identify the link object.
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.
|Load time property values||
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.
Unsupported test objects and methods
Only Web test object steps can run on Safari. All other steps run locally on the UFT computer, including Web 2.0 test objects or Web Add-in Extensibility-based test objects.
Additionally, the following specific test objects and test object methods are not supported when running on Safari:
Drag & Drop methods (on all Web test objects)
Web test objects located inside iFrame controls with a blank or about:blank SRC value.
- WebAudio.Play and WebVideo.Play methods
- WebAgGrid and WebUIGrid objects
|Opening a new browser tab||
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.
|Mouse replay types||
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).
|Back / Forward operations||
Performing Back or Forward options on Safari version 9 (El Capitan) causes unexpected behavior in UFT.
Workaround: Do the following:
Remote Mac connections
|Using the automation object model||
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.
Depending on the performance of your connection to the Mac, statement completion for the Object property might not work.