When you are testing a Web application in Google Chrome, locator recording in windows fails when multiple windows are open during application configuration in the Google Chrome instance, in which the application is running. If you close the other Google Chrome windows during application configuration, the error will not appear.
When you want to test a Web application with Google Chrome and the Continue running background apps when Google Chrome is closed check box is checked, Silk Test cannot restart Google Chrome to load the automation support.
If Windows Aero functionality is disabled, modal dialogs are not recognized and locators in such dialogs cannot be selected. As a workaround, use the Locator Spy or the Identify Object dialog box to manually create and verify locators while a modal dialog is displayed.
With Google Chrome 42 or later, Google Chrome by default blocks the NPAPI plug-in, which is used to display embedded PDFs. Because of this, Silk Test does not display embedded PDFs in Google Chrome 42 or later, but instead downloads the embedded PDFs.
Error executing '*'. Communication with browser automation timed out.
To avoid such connection timeouts, ensure that the test machine has enough processing power. For example, if you are testing on a slow virtual machine (VM), you could enhance the processing power by adding an additional CPU core to the VM.
If the user data directory is set as a policy in the registry through the key HKEY_LOCAL_MACHINE\Software\Policies\Google\Chrome\UserDataDir or the key HKEY_CURRENT_USER\Software\Policies\Google\Chrome\UserDataDir, and you are testing a web application on Google Chrome 66 or later, the base state might fail with the following error message: Failed to start application 'GoogleChrome'. unknown error: DevToolsActivePort file doesn't exist . This is a known issue in ChromeDriver: https://bugs.chromium.org/p/chromedriver/issues/detail?id=2513.