Skip to content
Allure report logoAllure Report
Main Navigation ModulesDocumentationStart

English

Español

English

Español

Appearance

Sidebar Navigation

Introduction

Install & Upgrade

Install for Windows

Install for macOS

Install for Linux

Install for Node.js

Upgrade Allure

Getting started

How to view a report

Improving readability of your test reports

Improving navigation in your test report

Features

Test steps

Attachments

Test statuses

Sorting and filtering

Defect categories

Visual analytics

Test stability analysis

History and retries

Timeline

Export to CSV

Export metrics

Guides

JUnit 5 parametrization

JUnit 5 & Selenide: screenshots and attachments

JUnit 5 & Selenium: screenshots and attachments

Setting up JUnit 5 with GitHub Actions

Pytest parameterization

Pytest & Selenium: screenshots and attachments

Pytest & Playwright: screenshots and attachments

Pytest & Playwright: videos

Playwright parameterization

How it works

Overview

Test result file

Container file

Categories file

Environment file

Executor file

History files

Integrations

Azure DevOps

Bamboo

GitHub Actions

Jenkins

JetBrains IDEs

TeamCity

Visual Studio Code

Frameworks

Behat

Getting started

Configuration

Reference

Behave

Getting started

Configuration

Reference

Codeception

Getting started

Configuration

Reference

CodeceptJS

Getting started

Configuration

Reference

Cucumber.js

Getting started

Configuration

Reference

Cucumber-JVM

Getting started

Configuration

Reference

Cucumber.rb

Getting started

Configuration

Reference

Cypress

Getting started

Configuration

Reference

Jasmine

Getting started

Configuration

Reference

JBehave

Getting started

Configuration

Reference

Jest

Getting started

Configuration

Reference

JUnit 4

Getting started

Configuration

Reference

JUnit 5

Getting started

Configuration

Reference

Mocha

Getting started

Configuration

Reference

Newman

Getting started

Configuration

Reference

NUnit

Getting started

Configuration

Reference

PHPUnit

Getting started

Configuration

Reference

Playwright

Getting started

Configuration

Reference

pytest

Getting started

Configuration

Reference

Pytest-BDD

Getting started

Configuration

Reference

Reqnroll

Getting started

Configuration

Reference

REST Assured

Getting started

Configuration

Robot Framework

Getting started

Configuration

Reference

RSpec

Getting started

Configuration

Reference

SpecFlow

Getting started

Configuration

Reference

Spock

Getting started

Configuration

Reference

TestNG

Getting started

Configuration

Reference

Vitest

Getting started

Configuration

Reference

WebdriverIO

Getting started

Configuration

Reference

xUnit.net

Getting started

Configuration

Reference

On this page

Allure WebdriverIO configuration ​

The Allure WebdriverIO adapter behavior can be affected by some configuration options set in your project's wdio.conf.js file.

To set the options, define an object after the "allure" string in the reporters configuration section. For example:

ts
import * as os from "os";

export const config = {
  // ...
  reporters: [
    "spec",
    [
      "allure",
      {
        outputDir: "allure-results",
        issueLinkTemplate: "https://issues.example.com/{}",
        tmsLinkTemplate: "https://tms.example.com/{}",
        reportedEnvironmentVars: {
          os_platform: os.platform(),
          os_release: os.release(),
          os_version: os.version(),
          node_version: process.version,
        },
      },
    ],
  ],
};

Common parameters ​

issueLinkTemplate, tmsLinkTemplate ​

Define templates that can be used to construct full URLs from short identifiers, see the reference. The pattern must contain {} at the position where the identifier should be placed.

outputDir ​

Path to the directory where Allure WebdriverIO will save the test results, see How it works. If the directory does not exist, it will be created. Defaults to allure-results.

reportedEnvironmentVars ​

Key-value pairs that will be displayed on the report's main page, see Environment information.

Steps and attachments ​

addConsoleLogs ​

If true, Allure WebdriverIO will automatically create an attachment containing all the console output produced by the test, i.e., all the messages passed to console.log().

disableWebdriverScreenshotsReporting ​

If true, Allure WebdriverIO will not automatically create an attachment with each screenshot taken via the WebdriverIO's saveScreenshot() function.

Note that you can always add screenshots manually by passing their file paths to Allure's attach().

disableWebdriverStepsReporting ​

If true, Allure WebdriverIO will not automatically create steps for each WebDriver command.

Runner-specific parameters ​

disableMochaHooks ​

This option is only relevant if you use the Mocha test runner.

If true, Allure WebdriverIO will not add Mocha hooks to the test report.

useCucumberStepReporter ​

This option is only relevant if you use the Cucumber.js test runner.

  • If false (or omitted), each Gherkin step will be displayed as a separate test. Allure will group together steps from the same Gherkin feature and scenario by default. You can move individual steps to other locations in the hierarchies by calling the corresponding functions, see Behavior-based hierarchy and Suite-based hierarchy.

    Note that if you use Scenario Outline to perform the same steps with different values, this may result in multiple steps with identical names in the test report. It is recommended to sort tests by order of execution when viewing such a report.

    Also note that with this option, Allure WebdriverIO does not support setting issue links and TMS links via Gherkin tags.

  • If true, Allure will treat each Gherkin scenario as a test, with Gherkin steps displayed as test steps. If your step definition calls the allureReporter.step() function, it will create a sub-step within the current step.

    Note that if you use Scenario Outline to perform the same steps with different values, Allure WebdriverIO will not be able to report it properly with this option turned on. Instead, the test report will only display the steps executed with the last set of values.

Pager
Previous pageGetting started
Next pageReference
Powered by

Join our newsletter

Allure TestOps
  • Overview
  • Why choose us
  • Cloud
  • Self-hosted
  • Success Stories
Company
  • Documentation
  • Blog
  • About us
  • Contact
  • Events
© 2025 Qameta Software Inc. All rights reserved.