<commit_before>WDIO ChromeDriver Service
================================

(Based entirely on [wdio-selenium-standalone-service](https://github.com/webdriverio/webdriverio/tree/master/packages/wdio-selenium-standalone-service).)

Note - starting with version 5.0.0, this service is targeted at WDIO v5. If you're working with WDIO v4, use latest version _before_ 5.0.0!

----

This service helps you to run ChromeDriver seamlessly when running tests with the [WDIO testrunner](http://webdriver.io/guide/testrunner/gettingstarted.html). It uses the [chromedriver](https://www.npmjs.com/package/chromedriver) NPM package that wraps the ChromeDriver for you.

Note - this service does not require a Selenium server, but uses ChromeDriver to communicate with the browser directly.
Obvisously, it only supports:

```js
capabilities: [{
        browserName: 'chrome'
    }]
```

## Installation

The easiest way is to keep `wdio-chromedriver-service` as a devDependency in your `package.json`.

```json
{
  "devDependencies": {
    "wdio-chromedriver-service": "^5.0.0"
  }
}
```

You can simple do it by:

```bash
npm install wdio-chromedriver-service --save-dev
```

Note! You have to install [chromedriver](https://www.npmjs.com/package/chromedriver)  separately, as it's a peerDependency of this project, and you're free to choose what version to use. Install it using:

```bash
npm install chromedriver --save-dev
```

Instructions on how to install `WebdriverIO` can be found [here.](http://webdriver.io/guide/getstarted/install.html)

## Configuration

By design, only Google Chrome is available (when installed on the host system). In order to use the service you need to add `chromedriver` to your service array:

```js
// wdio.conf.js
export.config = {
  // port to find chromedriver
  port: 9515, // default for ChromeDriver
  path: '/',
  // ...
  services: ['chromedriver'],

  // options
  chromeDriverArgs: ['--port=9515', '--url-base=\'/\''], // default for ChromeDriver
  chromeDriverLogs: './',
  // ...
};
```

## Options

### chromeDriverArgs
Array of arguments to pass to the ChromeDriver executable, see [https://helpmanual.io/help/chromedriver](https://helpmanual.io/help/chromedriver).
* `--port` will use wdioConfig.port if not specified
* `--url-base` will used wdioConfig.path if not specified

Type: `string[]`
### chromeDriverLogs
Path where all logs from the ChromeDriver server should be stored.

Type: `string`



----

For more information on WebdriverIO see the [homepage](http://webdriver.io).<commit_msg>chromedriver: update readme<commit_after>WDIO ChromeDriver Service
================================

(Based entirely on [wdio-selenium-standalone-service](https://github.com/webdriverio/webdriverio/tree/master/packages/wdio-selenium-standalone-service).)

Note:
If you're working with WebdriverIO v6, use version 6.X.X\
If you're working with WebdriverIO v5, use version 5.X.X\
If you're working with WebdriverIO v4, use version 4.X.X\

----

This service helps you to run ChromeDriver seamlessly when running tests with the [WDIO testrunner](http://webdriver.io/guide/testrunner/gettingstarted.html). It uses the [chromedriver](https://www.npmjs.com/package/chromedriver) NPM package that wraps the ChromeDriver for you.

Note - this service does not require a Selenium server, but uses ChromeDriver to communicate with the browser directly.
Obvisously, it only supports:

```js
capabilities: [{
        browserName: 'chrome'
    }]
```

## Installation

The easiest way is to keep `wdio-chromedriver-service` as a devDependency in your `package.json`.

```json
{
  "devDependencies": {
    "wdio-chromedriver-service": "^6.0.0"
  }
}
```

You can simple do it by:

```bash
npm install wdio-chromedriver-service --save-dev
```

Note! You have to install [chromedriver](https://www.npmjs.com/package/chromedriver)  separately, as it's a peerDependency of this project, and you're free to choose what version to use. Install it using:

```bash
npm install chromedriver --save-dev
```

Instructions on how to install `WebdriverIO` can be found [here.](http://webdriver.io/guide/getstarted/install.html)

## Configuration

By design, only Google Chrome is available (when installed on the host system). In order to use the service you need to add `chromedriver` to your service array:

```js
// wdio.conf.js
export.config = {
  outputDir: 'all-logs',
  // ...
  services: [
    ['chromedriver', {
        outputDir: 'driver-logs', // overwrites the config.outputDir
    }]
  ],
  // ...
};
```

## Options

### port
The port on which the driver should run on

Example: 7676

Type: `number`

### path
The path on which the driver should run on

Example:  `/wd/hub`

Type: `string`

### protocol
The protocol on which the driver should use

Example:  `http`

Type: `string`

### hostname
The protocol on which the driver should use

Example:  `localhost`

Type: `string`

### outputDir
The path where the output of the ChromeDriver server should be stored.

Example: `driver-logs`

Type: `string`



----

For more information on WebdriverIO see the [homepage](http://webdriver.io).
{'fraction_non_alphanumeric': 0.1322637448640188, 'fraction_numerical': 0.006261005674036392, 'mean_word_length': 4.076464746772592, 'pattern_counts': {'":': 4, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 8, 'lorem ipsum': 0, 'www.': 4, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '3645803', 'n_tokens_mistral': 1647, 'n_tokens_neox': 1526, 'n_words': 536}