CODEWITHSUNDEEP
seleniumbehatsaucelabs
Benefit
Benefit

Reputation: 11

"Your test errored. Test did not see a new command for 90 seconds. Timing out." Saucelabs

I am getting the error when i run test cases on suacelabs. I would like to increase the timeout to 180 seconds.

I tried this

 capabilities: {'platform':'OS X 10.10', 'browser':'chrome', 'version':'45.0', 'idleTimeout':'90'}

I am getting this error

[Symfony\Component\Config\Definition\Exception\InvalidConfigurationException]
Unrecognized option "idleTimeout" under "testwork.mink.sessions.selenium2.selenium2.capabilities"

Upvotes: 0

Views: 2742

Answers (3)

Parry
Parry

Reputation: 56

add driver.quit() along with driver.close()

If your tests don't include a session ending request, such as a call to driver.quit() or browser.stop(), they will will keep running forever, consuming all test minutes available in your account. This error is thrown after 90 seconds as a means of preventing this.

Hope it helps.

Upvotes: 1

oboeCoder
oboeCoder

Reputation: 186

The idleTimeout is the time that the session will stay alive without receiving a selenium command. The default setting is 90 seconds and the max is 1000 seconds. To set a timeout of 180 seconds, try the following configuration:

caps = {'browserName': "chrome"}
caps['platform'] = "OS X 10.10"
caps['version'] = "45.0"
caps['idleTimeout'] = 180

This is a Python example. Examples in other languages can be found here.

Upvotes: 1

djangofan
djangofan

Reputation: 29689

Just a guess, but maybe the format of the idleTimeout is wrong? Try variations on that, like this:

capabilities: {'platform':'OS X 10.10', 'browser':'chrome',
   'version':'45.0', 'idle-timeout':90}

Upvotes: 0

Related Questions