@christian-bromann/webdriverio
Version:
A nodejs bindings implementation for selenium 2.0/webdriver
60 lines (41 loc) • 2.12 kB
Markdown
name: allure
category: reporters
tags: guide
index: 3
title: WebdriverIO - Allure Reporter
---
Allure Reporter
===============
The Allure Reporter creates [Allure](http://allure.qatools.ru/) test reports which is an HTML generated website with all necessary information to debug your test results and take a look on error screenshots. To use it just install it from NPM:
```js
$ npm install wdio-allure-reporter --save-dev
```
Then add `allure` to the `reporters` array in your wdio.conf.js and define the output directory of the allure reports:
```js
// wdio.conf.js
exports.config = {
// ...
reporters: ['dot', 'allure'],
reporterOptions: {
allure: {
outputDir: 'allure-results'
}
},
// ...
}
```
`outputDir` defaults to `./allure-results`. After a test run is complete, you will find that this directory has been populated with an `.xml` file for each spec, plus a number of `.txt` and `.png` files and other attachments.
The results can be consumed by any of the [reporting tools](http://wiki.qatools.ru/display/AL/Reporting) offered by Allure. For example:
Install the [Allure Jenkins plugin](http://wiki.qatools.ru/display/AL/Allure+Jenkins+Plugin), and configure it to read from the correct directory:

Jenkins will then offer a link to the results from the build status page:

Install the [Allure command-line tool](https://www.npmjs.com/package/allure-commandline), and process the results directory:
```sh
$ allure generate [allure_output_dir] && allure report open
```
This will generate a report (by default in `./allure-report`), and open it in your browser:
