Forum Discussion
Thank you for the reply. Well, Ranorex is able to control these elements and it works quite well in our tests. Now the big question is, how to deal with such kind of elements in TC? The thing is, it's not just a question of this particular page, but there are also other Chrome UI elements, which needs to be occasionally controlled by tests. For example "Restore pages" popup and similar "native window" elements.
To handle the Chrome "Restore" popup, you can try the following:
- Navigate to the following path: C:\Users\<username>\AppData\Local\Google\Chrome\User Data\Default
- Search Preferences file
- Open file with notepad (or similar)
- Search the value "exit_type":"Crashed" and change it to "exit_type": "none"
- Search "exited_cleanly" and it should be "exited_cleanly":true
- Save & Close the preferences file
- Right-click on the file and make it read-only else chrome will update this file again with initial values
I have a brief post on how to run TestComplete using the latest browser version of Chrome and some things you can do to mitigate auto-update [here].
For the issue of bypassing the "connection is not private" page, you can try one of the following:
- Click a blank section of the denial page.
- Using your keyboard, type "thisisunsafe". This will add the website to a safe list, where you should not be prompted again
OR
This option will only work for requests to localhost over HTTP.
- In the Chrome address bar, type “chrome://flags/#allow-insecure-localhost“
- Select the “Enable” link.