Test does not start

[KadircanBoztepe]

the gauge scenario is starting and "test started" written on console but it's stuck at this point. i use below versions.

/opt/homebrew/bin/gauge run --machine-readable --hide-suggestion --simple-console /xxxx
Testing started at 00:53 ...

Process finished with exit code 137 (interrupted by signal 9: SIGKILL)

Gauge version: 1.4.1
html-report (4.1.2)
java (0.7.15)
screenshot (0.1.0)
xml-report (0.2.3)

pom.xml

com.thoughtworks.gauge
gauge-java
0.7.15

[sriv]

hi - does this happen with a specific project or is this something that you see across gauge projects in your machine?

[mertmansuroglu]

Hello, I also faced the same problem while trying to install gauge on my mac. Basically, in my terminal, I put "brew install gauge". Then, installed the gauge install components which in turn , initiated the test from example.spec. However, it's stuck at this point where the author of the issue has mentioned. I am facing this issue in all of my projects with gauge. You can see the ss below regarding the problem. Could you please help me if you have found the solution?

[sriv]

What version of java are you on @mertmansuroglu ?

Also, are you able to run the tests from your terminal using gauge run specs ?

FWIW, I am on

Gauge version: 1.4.1
Plugins
-------
dotnet (0.4.1)
html-report (4.1.2)
inprogress (0.2.0)
java (0.7.15)
js (2.3.17)
python (0.3.17)
screenshot (0.1.0)
ts (0.1.0)
xml-report (0.2.3)

And I am using OpenJDK 14.

Running gauge init java and then gauge run specs works fine for me, so I am still trying to guess what is different in yours (and also @KadircanBoztepe 's) projects/environments.

[mertmansuroglu]

Hello, here i have seen this screen after running the command "gauge run specs" Also, I have added the required info you have asked

[sriv]

hi, it seems that your project uses selenium, and if you have initialized a maven(or gradle) based template, you need to use those tools to run the project.

For ex: if you ran gauge init java_maven_selenium then the tests need to be run using mvn test or mvn test-compile gauge:execute

[mertmansuroglu]

Hello there, we again faced a similar issue regarding stuck while running the spec file. When we tried by setting the timeout to 10000 ms, the following error came "Failed to start gauge API: Timed out connecting to java" Basically, in the same module, API specs can run perfectly whereas Mobile specs showed the same problem mentioned above. Also, we tried with different java versions to fix the issue but still no luck. You can have a look at the log file below, gauge version with plugin and pom file. By the way, In our project, we are getting use of multipom mechanism, that is a parent pom is set which is covering three different poms called api, mobile and web.

Note: Another point we want mention is, we cannot debug from spec file using intellij which says connection refused in the console.

gauge.log gauge logs here