Problem with Test Suite Collection execution from cmd after migrating to 6.0.5

Hi,

After upgrading to Katalon Studio 6.0.5, I noticed that ordering Test Suite Collection execution is not longer possible from cmd on Windows 10.

My command is working perfectly on 5.10.1 version:
"C:\Program Files\Katalon_Studio_Windows_64-5.10.1\katalon.exe" -noSplash -runMode=console -consoleLog -noExit -projectPath="C:\projects\xxxxxx_selenium\katalon_xxxxxx\xxxxxx_demo\xxxxxx_demo.prj" -retry=0 -testSuiteCollectionPath="Test Suites/xxxxxx_demo"

However, running it from another, 6.0.5 executable, produces following error:
"C:\Program Files\Katalon_Studio_Windows_64-6.0.5\katalon.exe" -noSplash -runMode=console -consoleLog -noExit -projectPath="C:\projects\xxxxxx_selenium\katalon_xxxxxx\xxxxxx_demo\xxxxxx_demo.prj" -retry=0 -testSuiteCollectionPath="Test Suites/xxxxxx_demo"

Stacktrace:
!ENTRY org.eclipse.core.resources 2 10035 2019-03-01 18:11:32.602
!MESSAGE The workspace exited with unsaved changes in the previous session; refreshing workspace to recover changes.
Starting Groovy-Eclipse compiler resolver. Specified compiler level: unspecified
169 2.4.7.xx-201611170128-e46 = ACTIVE
Parsing custom keywords…
Generating global variables…
Project ‘xxxxxx_demo’ opened
com.kms.katalon.execution.exception.ExecutionException: Test suite ‘’{0}’’ has no test case to execute. Please check again.
at com.kms.katalon.execution.launcher.TestSuiteCollectionConsoleLauncher.buildSubLaunchers(TestSuiteCollectionConsoleLauncher.java:79)
at com.kms.katalon.execution.launcher.TestSuiteCollectionConsoleLauncher.newInstance(TestSuiteCollectionConsoleLauncher.java:53)
at com.kms.katalon.execution.console.entity.TestSuiteCollectionLauncherOptionParser.getConsoleLauncher(TestSuiteCollectionLauncherOptionParser.java:53)
at com.kms.katalon.execution.console.ConsoleExecutor.execute(ConsoleExecutor.java:74)
at com.kms.katalon.execution.console.ConsoleMain.launch(ConsoleMain.java:133)
at com.kms.katalon.console.application.Application.runConsole(Application.java:76)
at com.kms.katalon.core.application.Application.runConsole(Application.java:80)
at com.kms.katalon.core.application.Application.start(Application.java:63)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:388)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:243)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:673)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:610)
at org.eclipse.equinox.launcher.Main.run(Main.java:1519)

2 Likes

I have the same issue. Anyone have an answer ?

I’m having the same issue - If we have a Test Suite, and in that Test Suite we have test cases but all of them aren’t selected to be run. `Console log, in Jenkins (Linux) will show something like this:

com.kms.katalon.execution.exception.ExecutionException: Test suite ''{0}'' has no test case to execute. Please check again.
	at com.kms.katalon.execution.launcher.TestSuiteCollectionConsoleLauncher.buildSubLaunchers(TestSuiteCollectionConsoleLauncher.java:79)
	at com.kms.katalon.execution.launcher.TestSuiteCollectionConsoleLauncher.newInstance(TestSuiteCollectionConsoleLauncher.java:53)
	at com.kms.katalon.execution.console.entity.TestSuiteCollectionLauncherOptionParser.getConsoleLauncher(TestSuiteCollectionLauncherOptionParser.java:53)
	at com.kms.katalon.execution.console.ConsoleExecutor.execute(ConsoleExecutor.java:74)
	at com.kms.katalon.execution.console.ConsoleMain.launch(ConsoleMain.java:133)
	at com.kms.katalon.console.application.Application.runConsole(Application.java:76)
	at com.kms.katalon.core.application.Application.runConsole(Application.java:80)
	at com.kms.katalon.core.application.Application.start(Application.java:63)
	at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:388)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:243)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:673)
	at org.eclipse.equinox.launcher.Main.basicRun(Main.java:610)
	at org.eclipse.equinox.launcher.Main.run(Main.java:1519)
	at org.eclipse.equinox.launcher.Main.main(Main.java:1492)`

But if we try to run the same TS from GUI mode, as an output we will have the name of TS that contains TCs but all of them aren’t checked to be run.
If I run that Test Suite again, but this time directly from CLI (without using Jenkins), as a response I’ll get proper name, e.g.: Test suite 'Test' not found.
The most strange thing is that I never used a TS named “Test”
Tested on Linux with Jenkins. v.6.0.5

Sorry for the inconvenience. Please follow up in the above thread.

1 Like