Help: Katalon not running properly on Jenkins


#1

Need your help guys. I’m running my tests thru jenkins in virtual machine, but it throws itself to a never ending loop and the build never stops. i had to manually terminate the job for the build to stop. i tried running my command arguments in cmd itslef and it works. I tried everything that the docs and instructions on proper integration to jenkins states, but to no avail.

here is my command argument:
-projectPath=“C:\Katalon\com.ULGO.project\com.ULGO.project.prj” -retry=0 -testSuitePath=“Test Suites/GMA.E2E.Login Page” -executionProfile=“default” -browserType=“Chrome”

here is the console from the build:

Building in workspace C:\Program Files (x86)\Jenkins\workspace\GMA_E2E
Using Katalon Studio at C:\Katalon\Katalon_Studio_Windows_64-6.1.1
Execute [cmd, /c, C:\Katalon\Katalon_Studio_Windows_64-6.1.1\katalon -noSplash -runMode=console -projectPath=“C:\Katalon\com.ULGO.project\com.ULGO.project.prj” -retry=0 -testSuitePath=“Test Suites/GMA.E2E.Login Page” -executionProfile=“default” -browserType=“Chrome” ] in C:\windows\TEMP\katalon-8847307695314887296
Delete folder: bin
Delete folder: Libs
Opening project file: C:\Katalon\com.ULGO.project\com.ULGO.project.prj
Starting Groovy-Eclipse compiler resolver. Specified compiler level: unspecified
169 2.4.7.xx-201611170128-e46 = ACTIVE
Generating global variables…
Parsing custom keywords…
Project ‘com.ULGO.project’ opened

Test Suites/GMA.E2E.Login Page - Chrome - 20190417_092913…0/1(0%)

2019-04-17 09:29:17.437 INFO c.k.katalon.core.main.TestSuiteExecutor - START Test Suites/GMA.E2E.Login Page
2019-04-17 09:29:17.499 INFO c.k.katalon.core.main.TestSuiteExecutor - hostName = GMAEEAUTO-WVM$ - GMAEEAUTO-WVM.jene3dwzkssebmwdnk5e1y1s2a.ix.internal.cloudapp.net
2019-04-17 09:29:17.501 INFO c.k.katalon.core.main.TestSuiteExecutor - os = Windows Server 2016 64bit
2019-04-17 09:29:17.502 INFO c.k.katalon.core.main.TestSuiteExecutor - hostAddress = 172.16.3.4
2019-04-17 09:29:17.503 INFO c.k.katalon.core.main.TestSuiteExecutor - katalonVersion = 6.1.1.1
2019-04-17 09:29:18.116 INFO c.k.katalon.core.main.TestCaseExecutor - --------------------
2019-04-17 09:29:18.116 INFO c.k.katalon.core.main.TestCaseExecutor - START Test Cases/LoginUsingValidAccount
2019-04-17 09:29:18.860 DEBUG testcase.LoginUsingValidAccount - 1: openBrowser(“https://e2e-dev.ctech-ul.com/”)
2019-04-17 09:29:19.340 INFO c.k.k.core.webui.driver.DriverFactory - Starting ‘Chrome’ driver
2019-04-17 09:29:19.388 INFO c.k.k.core.webui.driver.DriverFactory - Action delay is set to 0 seconds
2019-04-17 09:29:26.063 INFO c.k.k.core.webui.driver.DriverFactory - sessionId = 9ba05640844b4739380979a80374be44
2019-04-17 09:29:26.207 INFO c.k.k.core.webui.driver.DriverFactory - browser = Chrome 73.0.3683.103
2019-04-17 09:29:26.212 INFO c.k.k.core.webui.driver.DriverFactory - platform = Windows Server 2016
2019-04-17 09:29:26.215 INFO c.k.k.core.webui.driver.DriverFactory - seleniumVersion = 3.7.1
2019-04-17 09:29:26.217 INFO c.k.k.core.webui.driver.DriverFactory - proxyInformation = ProxyInformation{proxyOption=NO_PROXY, proxyServerType=HTTP, password=, proxyServerAddress=, proxyServerPort=0}

Test Suites/GMA.E2E.Login Page - Chrome - 20190417_092913…0/1(0%)

2019-04-17 09:29:29.200 DEBUG testcase.LoginUsingValidAccount - 2: maximizeWindow()

Test Suites/GMA.E2E.Login Page - Chrome - 20190417_092913…0/1(0%)


Test Suites/GMA.E2E.Login Page - Chrome - 20190417_092913…0/1(0%)


Test Suites/GMA.E2E.Login Page - Chrome - 20190417_092913…0/1(0%)


Test Suites/GMA.E2E.Login Page - Chrome - 20190417_092913…0/1(0%)


Test Suites/GMA.E2E.Login Page - Chrome - 20190417_092913…0/1(0%)


Test Suites/GMA.E2E.Login Page - Chrome - 20190417_092913…0/1(0%)


Test Suites/GMA.E2E.Login Page - Chrome - 20190417_092913…0/1(0%)


#2

I’m seeing similar behavior intermittently with my jenkins builds as well.

My tests are pretty simple get request that verify a repsonse code is between 200-399. I’m using the Katalon plugin as well. The tests appear to all run fine when they are passing, but when there’s a failure it goes into an infinite loop as mentioned above.

I’m also seeing behavior where Katalon occasionally gets into a bad state and I’ll have to clear out the config/.metadata/.plugins folder, and then it will work again. I could write a script to do this before each job, but is that necessary?