- Getting Started with Selenium for Automated Website Testing
- Getting Started with Appium for Mobile Native Application Testing
- Selenium Bootcamp by Dave Haeffner
- Appium Bootcamp by Dave Haeffner and Matthew Edwards
You'll see this error when Sauce Labs doesn't receive a new command from your Selenium script in more than 90 seconds (the default duration for a timeout).
There are a couple potential causes for this error.
- The most common cause is that your script crashed, was forcefully interrupted, or you lost internet connectivity
- If your tests don't include a session ending request, such as a call to
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.
- A less common, but still possible cause, is that your test legitimately needs more than 90 seconds to send a new command to the browser. This happens most often when a network or disk IO error occurs between Selenium API calls in your tests (for example, for DB queries, local file reads, or changes).
How to Resolve
- Make sure you have internet connectivity
- Make sure your script includes
browser.stop()to conclude the test
- If your test needs more than 90 seconds to send a new command to the browser, use the
idleTimeoutdesired capability to modify Sauce's wait time for further commands. You can find out more about this desired capability in the Timeouts section of the Test Configuration Options topic.