Last updated: Aug 27, 2017 15:41
Extend the timeout on the RemoteWebDriver or AppiumDriver creation to avoid timeout when installing an application,
starting up multiple applications for Wind Tunnel testing, or performing download report (for large report files).
The constructor of the Selenium or Appium driver supports a timeout parameter in addition to the standard URL and DesiredCapabilities parameters.
By default, the timeout on the driver instantiation is set to 1 minute (60 seconds). However, if your capabilities include starting several applications, for example if you are using a Wind Tunnel persona, or if you specify a large application for installation by the Appium driver this may cause the processing to extend beyond this timeout period and you may receive the following exception dump (in Visual Studio/C#) from the test script:
If the following message is included in the exception: timed out after 60seconds. --->System.Net.WebException: The operation has timed out. it is an indication that you need an extended driver creation timeout.
To define the longer timeout (for example 4 minutes) use the appropriate following format:
For C# or Java:
Using Perfecto's RemoteWebDriverExtended class:
The exception (Net::ReadTimeout) will be reported as:
To set an extended RemoteWebDriver timeout in Ruby use the following: