I can not start Chrome from Katalon.


#1

Please watch this movie as it starts up.
(https://drive.google.com/file/d/1vt4Ev3Gwi1e6rSlYittKRT-hWWU5UMSD/view?usp=sharing)

Also attach Chrome Driver’s settings capture, so please watch it together as well.
(https://drive.google.com/open?id=1SPN2c0zYGp_qfX2CNynfsGxXS_Ks1YmE)

Remark 1: Firefox can start the browser normally.
Remark 2: Error message outputted when Chrome starts up is here


#2

Where is it? I can not find it.


#3

chromedriver.log would be helpful. see the following post how to get it.


#4

Hello,

Your screen capture also tells us that you are on an API/WebService project, but doing UI testing.

Can you create a Web project and see if you have the same behaviour ?

image


#5

Sorry, I forgot to write error message.
I write now!

openBrowser("") FAILED.
Reason:
com.kms.katalon.core.exception.StepFailedException: Unable to open browser with url: ‘’ (Root cause: org.openqa.selenium.WebDriverException: unknown error: Chrome failed to start: exited normally
(chrome not reachable)
(The process started from chrome location /Applications/Google Chrome.app/Contents/MacOS/Google Chrome is no longer running, so ChromeDriver is assuming that Chrome has crashed.)
(Driver info: chromedriver=2.43.600229 (3fae4d0cda5334b4f533bede5a4787f7b832d052),platform=Mac OS X 10.14.2 x86_64) (WARNING: The server did not provide any stacktrace information)
Command duration or timeout: 2.55 seconds
Build info: version: ‘3.7.1’, revision: ‘8a0099a’, time: ‘2017-11-06T21:07:36.161Z’
System info: host: ‘ML-00280noMacBook-Pro.local’, ip: ‘fe80:0:0:0:86d:751d:c1a1:831d%en0’, os.name: ‘Mac OS X’, os.arch: ‘x86_64’, os.version: ‘10.14.2’, java.version: ‘1.8.0_181’
Driver info: driver.version: CChromeDriver)
at com.kms.katalon.core.keyword.internal.KeywordMain.stepFailed(KeywordMain.groovy:36)
at com.kms.katalon.core.webui.keyword.internal.WebUIKeywordMain.stepFailed(WebUIKeywordMain.groovy:65)
at com.kms.katalon.core.webui.keyword.internal.WebUIKeywordMain.runKeyword(WebUIKeywordMain.groovy:27)
at com.kms.katalon.core.webui.keyword.builtin.OpenBrowserKeyword.openBrowser(OpenBrowserKeyword.groovy:81)
at com.kms.katalon.core.webui.keyword.builtin.OpenBrowserKeyword.execute(OpenBrowserKeyword.groovy:67)
at com.kms.katalon.core.keyword.internal.KeywordExecutor.executeKeywordForPlatform(KeywordExecutor.groovy:56)
at com.kms.katalon.core.webui.keyword.WebUiBuiltInKeywords.openBrowser(WebUiBuiltInKeywords.groovy:60)
at com.kms.katalon.core.webui.keyword.WebUiBuiltInKeywords$openBrowser.call(Unknown Source)
at sample.run(sample:16)
at com.kms.katalon.core.main.ScriptEngine.run(ScriptEngine.java:194)
at com.kms.katalon.core.main.ScriptEngine.runScriptAsRawText(ScriptEngine.java:119)
at com.kms.katalon.core.main.TestCaseExecutor.runScript(TestCaseExecutor.java:328)
at com.kms.katalon.core.main.TestCaseExecutor.doExecute(TestCaseExecutor.java:319)
at com.kms.katalon.core.main.TestCaseExecutor.processExecutionPhase(TestCaseExecutor.java:298)
at com.kms.katalon.core.main.TestCaseExecutor.accessMainPhase(TestCaseExecutor.java:290)
at com.kms.katalon.core.main.TestCaseExecutor.execute(TestCaseExecutor.java:224)
at com.kms.katalon.core.main.TestCaseMain.runTestCase(TestCaseMain.java:106)
at com.kms.katalon.core.main.TestCaseMain.runTestCase(TestCaseMain.java:97)
at com.kms.katalon.core.main.TestCaseMain$runTestCase$0.call(Unknown Source)
at TempTestCase1551863413770.run(TempTestCase1551863413770.groovy:22)


#6

I confirmed can I boot chrome in Web project.
Unfortunate, result was as same as when I used API/WebService project.


#7

satoshi,

Do you have any plugin installed in your chrome? Any plugin which you can not disable. For example, Skysea client view.

My previous experience may help.


#8

Hello all.

I’ve seen this error a lot of times, at least in my Windows box.
I suspect (not 100% sure) there is a bug in how Katalon opens browser sessions: if a previously opened browser session keeps open while the test has finished, Katalon refuses to connect with it. In fact, this is what the stack trace says (

)

The solution in my case always has been: kill all chrome processes (the button with the selectable list of browses must not show any session for Chrome) and restart the test.

I hope it helps !!