We are using Katalon Runtime Engine (KRE).
We are trying to use the –config -webui.autoUpdateDrivers=true option, to avoid issues when browsers have been updated.
We are focused on Chrome (which uses ChromeDriver driver) and Firefox (which uses Gecko driver).
The following takes place on a Windows10 machine.
Before using the autoUpdateDrivers option, we had observed that the drivers are stored in the C:\Katalon_Studio_Engine_Windows_64-8.1.0\configuration\resources\drivers “DRIVERS” sub-directories.
In the console log, when KRE is booting, KRE says:
chromedriver is located at default location: C:\Katalon_Studio_Engine_Windows_64-8.1.0\configuration\resources\drivers\chromedriver_win32\chromedriver.exe. In case your browser is updated to a newer version, please use this command to update chromdriver: --config -webui.autoUpdateDrivers=true
===> as the machine now runs Chrome 94, we expect an upgrade.
We use the --config -webui.autoUpdateDrivers=true option.
We have observed that, as a result, KRE creates a new “TEMP” directory and sub-directory.
In the console log, KRE says that it is now working with the new directory.
Chrome driver is located at: C:\Katalon_Studio_Engine_Windows_64-8.1.0\configuration\resources\temp\webdriver\chromedriver.exe
Indeed, the new drivers get downloaded in that “TEMP” sub-directory.
But KRE, when running the Test Suites, still tries to use the drivers from the “DRIVERS” sub-directories.
Indeed, if we just delete those (old) drivers from the “DRIVERS” sub-directories before running KRE, the Test Suites fail, with KRE logging:
Caused by: java.lang.IllegalStateException: The driver executable does not exist: C:\Katalon_Studio_Engine_Windows_64-8.1.0\configuration\resources\drivers\firefox_win64\geckodriver.exe
Caused by: java.lang.IllegalStateException: The driver executable does not exist: C:\Katalon_Studio_Engine_Windows_64-8.1.0\configuration\resources\drivers\chromedriver_win32\chromedriver.exe
The workaround looks easy: just copy from “TEMP” to “DRIVERS”…
copy temp\webdriver\geckodriver.exe drivers\firefox_win64
copy temp\webdriver\chromedriver.exe drivers\chromedriver_win32\
But this suggests that:
- either we are not using the autoUpdateDrivers option effectively,
- or there is an issue with the KRE product (it forgets to copy from “TEMP” to “DRIVERS”?)
Has anybody observed similar issues? What are we doing wrong?