My environment
- macOS 14.7.6
- Katalon Studio Free 10.2.1
Incident
I created a new katalon project based on the sample project “Healthcare tests”
I did “Update WebDriver” for Chrome.
Updating web driver...
Checking WebDriverManager
Verify built-in web driver manager
Using built-in file
[INFO] Using WebDriverManager to resolve chrome
[DEBUG] Detecting chrome version using online commands.properties
[DEBUG] Running command on the shell: [/Applications/Google Chrome.app/Contents/MacOS/Google Chrome, --version]
[DEBUG] Result: Google Chrome 137.0.7151.104
[INFO] Using chromedriver 137.0.7151.70 (resolved driver for Chrome 137)
[DEBUG] Using URL built from repository pattern: https://storage.googleapis.com/chrome-for-testing-public/137.0.7151.70/mac-x64/chromedriver-mac-x64.zip
[DEBUG] Driver to be downloaded chromedriver 137.0.7151.70
[INFO] Downloading https://storage.googleapis.com/chrome-for-testing-public/137.0.7151.70/mac-x64/chromedriver-mac-x64.zip
I ran the Test Case “TC1_Verify Successful Login”.
Then, I got the following display:
It said “demoaut.katalon.com doesn’t support a secure connection with HTTPS”. I was disturbed by this. But, when I click the button “Continue to site”, the test began running.
using different version
I downgraded Katalon Studio version v10.2.0. It behaved differently.
With v10.2.0, I was not disturbed by the display with “xxx doesn’t support a secure connection with HTTPS”.
Study
I could confirm that
- Katalon Studio v10.2.1 launched Chrome for Testing
- Katalon Studio v10.2.0 launched Chrome-branded Chromium (A.K.A, usual Google Chrome browser)
Workaround
I found the following Q&A in Stackoverflow
With v10.2.1, I configured the Project Settings>Desired Capability>WebUI>Chrome as follows:
I added an argument to Chrome:
--unsafely-treat-insecure-origin-as-secure=http://demoaut.katalon.com
Then testcase ran smoothly.
Discussion
The argument --unsafely-treat-insecure-origin-as-secure=http://xxxxxx.xxxx.xxx
takes a value, e.g, ‘demoaut.katalon.com’. I feel it is annoying to give that value for each individual cases.
It seems that Chrome for Testing warns about “insecure origins” but Google Chrome-branded Chromium doesn’t. Why? How Google Chrome-branded Chromium lets me work around the warning without any configuration? — I don’t know. Does anyone know it?
Katalon should add a new URL https://demoaut.katalon.com
in addition to the http://demoaut.katalon.com
, and modify the sample “Healthcare” project. I mean, Katalon should change the server of demoaut.katalon.com
so that it is reachable with scheme https:
.