Maximum count of request retries to the Selenium server.Īllows you to use a custom http/ https/ http2 agent to make requests. Timeout for any WebDriver request to a driver or grid. When running in standalone mode, the only log generated by WebdriverIO will be the wdio log. Since most reporters are made to log to stdout, it is recommended to only use this option for specific reporters where it makes more sense to push report into a file (like the junit reporter, for example). If not set, all logs are streamed to stdout. Options: trace | debug | info | warn | error | silent outputDir ĭirectory to store all testrunner log files (including reporter logs and wdio logs). If you’re running web or native tests on mobile devices, capabilities differs from the WebDriver protocol.

moz:firefoxOptions: for Mozilla FirefoxĪdditionally, a useful utility is the Sauce Labs Automated Test Configurator, which helps you create this object by clicking together your desired capabilities.

These are documented in the corresponding vendor docs, e.g.: Next to the WebDriver based capabilities you can apply browser and vendor specific options that allow deeper configuration to the remote browser or device. If you run an older driver that doesn't support the WebDriver protocol, you’ll need to use the JSONWireProtocol capabilities to successfully run a session. Check out the WebDriver Protocol for more details. If you don't use a cloud provider this can be used to authenticate any other WebDriver backend.ĭefines the capabilities you want to run in your WebDriver session. If set, WebdriverIO will automatically set connection options for you.

Your cloud service access key or secret key (only works for Sauce Labs, Browserstack, TestingBot, CrossBrowserTesting or LambdaTest accounts). If you don't use a cloud provider this can be used to authenticate any other WebDriver backend.

Your cloud service username (only works for Sauce Labs, Browserstack, TestingBot, CrossBrowserTesting or LambdaTest accounts). Query parameters that are propagated to the driver server.

Protocol to use when communicating with the driver server. The following options are defined when using the webdriver protocol package: protocol using the raw protocol bindings, WebdriverIO as standalone package or the WDIO testrunner) there is a different set of options available to control the environment.

Webdriver chrome download