Geek asks and answers

Work with timeouts at Sauce Labs

I have a web driver code that works without problems when working in a local browser instance. My code interacts with the browser, but has a period when it runs some background tasks through the terminal in order to configure the data for the rest of the test. This is a test from end to end, and must be performed in this order, leaving the browser inactive for a short period of time, usually up to 5 minutes. After completing the background tasks, the browser interacts with again.

Unfortunately, when I launch my remnants remotely from Sauce Labs, when starting background tasks, Sauce Labs considers the browser inactive for more than 90 seconds and suggests a problem. This leads to a failure, although the test is never interrupted. I can not find anything in the documentation regarding how to increase the idle timeout. Is there any way to do this?

+3
source share
2 answers

Saucelabs has several different types of timeouts:

  • Maximum Test Duration
  • Team Timeout
  • Invalid validation timeout

Additional information: https://saucelabs.com/docs/additional-config

Either the maximum duration or the idle timeout should help you. I think downtime still burns minutes of dough for the sauce.

+2

, :

desired_capabilities["idle-timeout"] = "180"

180 , ...

0

More articles:


All Articles