Forum Discussion

Camo's avatar
Occasional Contributor
4 years ago

Paralel test timeout error

I have few tests which run in parallel via maven surefire plugin. Sometimes about 8:1 some test crashes on error: org.openqa.selenium.ScriptTimeoutException: java.util.concurrent.TimeoutException It seems it is related to parallel run but I don't know how to fix it. Tests run against Selenium standalone server 4, which is on the same server as the test runner and teste application. Here is maven surefire plugin implemantation:


and here is the whole error log:

org.openqa.selenium.ScriptTimeoutException: java.util.concurrent.TimeoutException
Build info: version: '3.141.59', revision: 'e82be7d358', time: '2018-11-14T08:17:03'
System info: host: '', ip: '', 'Linux', os.arch: 'amd64', os.version: '5.4.0-70-generic', java.version: '11.0.10'
Driver info: org.openqa.selenium.remote.RemoteWebDriver
Capabilities {acceptInsecureCerts: true, browserName: chrome, browserVersion: 89.0.4389.114, chrome: {chromedriverVersion: 89.0.4389.23 (61b08ee2c5002..., userDataDir: /tmp/}, goog:chromeOptions: {debuggerAddress: localhost:42525}, javascriptEnabled: true, networkConnectionEnabled: false, pageLoadStrategy: normal, platform: LINUX, platformName: LINUX, proxy: Proxy(), se:cdp:, setWindowRect: true, strictFileInteractability: false, timeouts: {implicit: 0, pageLoad: 300000, script: 30000}, unhandledPromptBehavior: dismiss and notify, webauthn:extension:largeBlob: true, webauthn:virtualAuthenticators: true}
Session ID: 9eacdc08d0171e3ebc29cd2e7ae64cfc
	at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
	at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(
	at java.base/jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(
	at java.base/java.lang.reflect.Constructor.newInstance(
	at org.openqa.selenium.remote.http.W3CHttpResponseCodec.createException(
	at org.openqa.selenium.remote.http.W3CHttpResponseCodec.decode(
	at org.openqa.selenium.remote.http.W3CHttpResponseCodec.decode(
	at org.openqa.selenium.remote.HttpCommandExecutor.execute(
	at org.openqa.selenium.remote.RemoteWebDriver.execute(
	at org.openqa.selenium.remote.RemoteWebDriver.get(
	at org.openqa.selenium.remote.RemoteWebDriver$
	at com.codeborne.selenide.drivercommands.Navigator.lambda$navigateTo$0(
	at com.codeborne.selenide.drivercommands.Navigator.navigateTo(
	at steps.BaseSteps.openPage(
	at steps.admin.AdminPageSteps.logInAndOpenAdminPage(
	at ✽.User is logged in and is on admin page(file:///home/tatrytec/selenium-tests/


Thanks a lot for any help. I really don't know what is the problem.

4 Replies

  • There are so many reason for such error, but I'm not sure cucumber would have anything to do with it actually.


    • make sure the timeouts are not configured too low based on what you are trying to test: check and try increasing some
    • make sure you don't overload your test environment: parallel execution with selenium can easily overload a system resources - memory and CPU - specifically inside VMs or such environment: check the resources of your environment, maybe think about reducing the number of parallel execution
    • make sure your selenium automation is set-up properly, allowing several instances of the browser to be executed in parallel
    • Camo's avatar
      Occasional Contributor

      Can I ask which timeouts do you mean? Also how to set up number of parallel test properly? My settings comes from documentation. I did not find any other resources about it. 





      • The selenium timeouts, like the one that your are facing.

        To setup the number of parallel execution properly, it is up to you to check what can handle your system and to adjust.

        Which documentation are you talking about?