I’m trying to finalize running a Katalon Studio iOS test suite in a Team City build step. I was able to get everything running, however the cli test suite runner never stops its execution.
I use a custom build path for the application, so I put the application location in a global variable(g_appPath) so i can override it with the custom location in Team City
At the end of the test suite execution this is the behavior I’m seeing
[17:05:13] :
[Step 2/2] 2019-02-26 17:05:13.151 INFO c.k.katalon.core.main.TestSuiteExecutor - --------------------
[17:05:13] :
[Step 2/2] 2019-02-26 17:05:13.151 INFO c.k.katalon.core.main.TestSuiteExecutor - END Test Suites/All
[17:05:13] :
[Step 2/2] 2019-02-26 17:05:13.151 INFO c.k.katalon.core.main.TestSuiteExecutor - ====================
So running it manually in a terminal on the teamcity buildagent it does exit after the final report comes out, but Is there something i can do to make that happen in the teamcity cli command?
Thanks for your information. Please confirm these questions, that will help us investigate better:
If you run katalon directly from terminal without using TeamCity agent. It means you run the project on local machine like as a normal user, will the katalon process finish?
If you run katalon using TeamCity agent with a Test Suite that contains just one test case, will the katalon process finish?
It looks like updating the version of katalon helped with this issue. We upgraded katalon, and found that we had the -noExit flag still on in the Teamcity command. Once that was removed everything started working as expected.
Hi All,
I have encountered a similar issue, but unfortunately we don’t use the --noExit parameter in the command line.
We are able to launch simple test that only does an assert, but when we try to launch subcutaneous cucumber test on a remote web driver, the windows never seem to be closing and loop with this output 16:57:11 -------------------------------------------------------------------------------- 16:57:11 Test Suites/SystemTestSuccess - Firefox - 20190821_135511…1/1(100%) 16:57:11 -------------------------------------------------------------------------------- 16:57:26 -------------------------------------------------------------------------------- 16:57:26 Test Suites/SystemTestSuccess - Firefox - 20190821_135511…1/1(100%) 16:57:26 --------------------------------------------------------------------------------
The only time the test completed was when it was unable to connect to the remote web driver or when I killed the geckodriver.
We use this command line:
/opt/katalonstudio/katalon -runMode=console -projectPath=/home/jenkins/project/qa-katalon-develop.prj -testSuitePath=‘Test Suites/SystemTestSuccess’ --executionProfile=‘TEST-Z’ -reportFolder=’/tmp’ -browserType=‘Firefox (headless)’
When we launch this test from katalon studio, the test completed correctly.
When I tried the consoleLog I had the following information that could provide usefull
We have katalon Studio Version 5.10.1, we run it in a Jenkins(V2.176.2) Pipeline that is launch on a dynamic agent provide with an OpenShift(v3.6) Pod.
I’m facing a similar issue. My Test Suite runs on Linux machine through Command Line.
I don’t have -noExit parameter in the command. But, I still see that control doesn’t come out of Katalon even after Test Suite execution is completed and katalon process will still be alive.
If I kill the katalon process, control exits and return back to the calling method.
Also, this issue seems to be intermittent and more hung cases are seen than success.
The -consoleLog option is for running in interactive mode on Windows and should not be used on other platforms. This option has been removed in Katalon Runtime Engine 7.
