search

serenity-bdd / serenity-cucumber-starter

A skeleton project for Serenity BDD and Cucumber JVM
Apache License 2.0
180 stars 285 forks source link

Remote driver doesn't work with version 3.2.0 #70

Open krisz-unyi opened 2 years ago

krisz-unyi commented 2 years ago

Hi ,

It seems like serenity 3.2.0 doesn't work with remote driver. I tried to setup a chrome webdriver. I followed the offical description of selenium .

After setting up a chrome container like this : docker run -d -p 4444:4444 -p 7900:7900 --shm-size="2g" selenium/standalone-chrome:4.1.2-20220208

I changed the serenity-cucumber-starter's serenity.conf file

webdriver { driver = remote remote { url="http://localhost:4444" driver=chrome } }

After that I tried to run the tests which was working just fine with the chrome autodownload option.

webdriver { driver = chrome autodownload = true }

But I received this error message:

Feb 16, 2022 4:00:39 PM org.openqa.selenium.remote.tracing.opentelemetry.OpenTelemetryTracer createTracer INFO: Using OpenTelemetry for tracing Feb 16, 2022 4:00:54 PM org.openqa.selenium.remote.ProtocolHandshake createSession INFO: Detected dialect: W3C Feb 16, 2022 4:00:54 PM org.openqa.selenium.devtools.CdpVersionFinder findNearestMatch WARNING: Unable to find an exact match for CDP version 98, so returning the closest version found: 97 Feb 16, 2022 4:00:54 PM org.openqa.selenium.devtools.CdpVersionFinder findNearestMatch INFO: Found CDP implementation for version 98 of 97 Feb 16, 2022 4:01:04 PM org.openqa.selenium.remote.http.netty.NettyWebSocket lambda$new$0 WARNING: connection timed out: /172.19.0.22:4444 java.net.ConnectException: connection timed out: /172.19.0.22:4444 at org.asynchttpclient.netty.channel.NettyConnectListener.onFailure(NettyConnectListener.java:179) at org.asynchttpclient.netty.channel.NettyChannelConnector$1.onFailure(NettyChannelConnector.java:108) at org.asynchttpclient.netty.SimpleChannelFutureListener.operationComplete(SimpleChannelFutureListener.java:28) at org.asynchttpclient.netty.SimpleChannelFutureListener.operationComplete(SimpleChannelFutureListener.java:20) at io.netty.util.concurrent.DefaultPromise.notifyListener0(DefaultPromise.java:578) at io.netty.util.concurrent.DefaultPromise.notifyListeners0(DefaultPromise.java:571) at io.netty.util.concurrent.DefaultPromise.notifyListenersNow(DefaultPromise.java:550) at io.netty.util.concurrent.DefaultPromise.notifyListeners(DefaultPromise.java:491) at io.netty.util.concurrent.DefaultPromise.setValue0(DefaultPromise.java:616) at io.netty.util.concurrent.DefaultPromise.setFailure0(DefaultPromise.java:609) at io.netty.util.concurrent.DefaultPromise.tryFailure(DefaultPromise.java:117) at io.netty.channel.nio.AbstractNioChannel$AbstractNioUnsafe$1.run(AbstractNioChannel.java:262) at io.netty.util.concurrent.PromiseTask.runTask(PromiseTask.java:98) at io.netty.util.concurrent.ScheduledFutureTask.run(ScheduledFutureTask.java:170) at io.netty.util.concurrent.AbstractEventExecutor.safeExecute(AbstractEventExecutor.java:164) at io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:469) at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:503) at io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:986) at io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74) at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30) at java.base/java.lang.Thread.run(Thread.java:833) Caused by: io.netty.channel.ConnectTimeoutException: connection timed out: /172.19.0.22:4444 at io.netty.channel.nio.AbstractNioChannel$AbstractNioUnsafe$1.run(AbstractNioChannel.java:261)

When I use the serenity version 3.0.5 this issue is not present.

I'm looking forward to your answer. Regards, Krisztian

Related issue : https://github.com/serenity-bdd/serenity-core/issues/2663