Testing with Google Chrome

This section describes how you can enhance your cross-browser test set by testing with Google Chrome.

Silk4J supports recording actions and replaying tests on Google Chrome 50 or later, and supports replaying tests and recording locators on Google Chrome versions prior to version 50.

When starting to test on Google Chrome 50 or later, with no running instance of Google Chrome open, Silk4J starts a new instance of Google Chrome. This new browser uses a temporary profile without add-ons and with an empty cache.
When starting to test on an instance of Google Chrome 50 or later, which is already running, Silk4J restarts Google Chrome with the same command line arguments that were used when the instance was initially started. This restart is required to enable the Silk4J automation support.
When testing with Google Chrome 50 or later, the Google Chrome instance is closed when shutting down the Open Agent or when starting to test another application outside Google Chrome.

Tip: If you want to execute an existing test script with Google Chrome 50 or later, Micro Focus recommends that you use a base state or that you add a command to the test script to navigate to the URL.

Example 1

If the running instance of Google Chrome 50 or later was initially started with the command C:/Program Files (x86)/Google/Chrome/Application/chrome.exe www.borland.com, Google Chrome opens to www.borland.com after the restart.

Example 2

If the running instance of Google Chrome 50 or later was initially started with the command C:/Program Files (x86)/Google/Chrome/Application/chrome.exe, Google Chrome opens to about:blank after the restart.