(Based on wdio-selenium-standalone-service)
This service helps you to run Chromedriver or Geckodriver seamlessly when running tests with the WDIO testrunner. It uses:
Note - this service does not require a Selenium server, but uses ChromeDriver or GeckoDriver to communicate with the browser directly. It supports:
The easiest way is to keep
wdio-webdriver-service as a devDependency in your
You can simple do it by:
npm install wdio-webdriver-service --save-dev
Instructions on how to install
WebdriverIO can be found here.
To use the service you need to add
webdriver to your service array:
Path where all logs from the WebDriver server should be stored.
Type of the driver component to use.
Arguments to run driver component binary with. Note that options for Gecko driver and Chrome driver are different.
Gecko driver options:
-b BINARY/--binary BINARY Path to the Firefox binary to use. --connect-existing Connecting to an existing Firefox instance. --host HOST Host to use for the WebDriver server. Defaults to 127.0.0.1. --log LEVEL Set the Gecko and geckodriver log level. --marionette-port PORT Port to use for connecting to the Marionette remote protocol. -p PORT/--port PORT Port to use for the WebDriver server. Defaults to 4444.
Chrome driver options:
--port=PORT Port to listen on --adb-port=PORT Adb server port --verbose Log verbosely --version Print the version number and exit --silent Log nothing --url-base Base URL path prefix for commands, e.g. wd/url --port-server Address of server to contact for reserving a port --whitelisted-ips Comma-separated whitelist of remote IPv4 addresses which are allowed to connect to ChromeDriver
For more information on WebdriverIO see the homepage.