We're updating the issue view to help you get more done. 

Possibility to configure the CommandTimeout when creating a WebDriver

Description

WebTestHelper.OnFIxtureSetup() and WebTestHelper.CreateNewBrowserSession() accept a new optional DriverConfigurationOverride parameter, allowing to override the Selenium WebDrivers timeouts (SearchTimeout, RetryInterval, CommandTimeout).


Currently, when initialising a WebDriver inside our IBrowserFactory implementations (ChromeBrowserFactory, InternetExplorerBrowserFactory), no CommandTimeout is supplied and therefore the Default Command Timeout of 60 second is used. We currently offer no easy way to configure this Command Timeout (other than implementing your own BrowserFactory). 

Configuring this timeout could be desireable in an environment, where the command timeout is sometimes reached, because some service is not started (resulting in an OpenQA.Selenium.WebDriverException The HTTP request to the remote WebDriver server for URL http://localhost:46637/session/0181bad7430af341b5bb0161afe6b148/elements timed out after 60 seconds ). The desired configuration would be a shorter Timeout, so tests fail faster in such cases. Maybe it would also make sense to use the already configurable searchTimeout for the CommandTimeout (although it should be tested beforehand what a sensible CommandTimeout is, and if it is just about the value of our searchTimeout).

Status

Assignee

Marcel Holle

Reporter

Florian Decker

Labels

None

Time tracking

3h

Components

Fix versions

Priority

Normal
Configure