---
title: Cucumber.js
description: Learn how to integrate Allure with Cucumber.js to generate rich, interactive test reports. Follow step-by-step setup, test execution, and report generation guidance.
---

# Getting started with Allure Cucumber.js

[![Allure Cucumber.js npm latest version](https://img.shields.io/npm/v/allure-cucumberjs?style=flat "Allure Cucumber.js npm latest version")](https://www.npmjs.com/package/allure-cucumberjs)

Generate beautiful HTML reports using [Allure Report](https://allurereport.org/docs/) and your [Cucumber.js](https://cucumber.io/docs/installation/javascript/) tests.

Info:
Check out the example projects at [github.com/allure-examples](https://github.com/orgs/allure-examples/repositories?q=visibility%3Apublic+archived%3Afalse+topic%3Aexample+topic%3Acucumberjs) to see Allure Cucumber.js in action.

## Setting up

### 1. Prepare your project

1. Make sure [Node.js](https://nodejs.org/) is installed.

   Allure Cucumber.js is tested against Node.js 18 and higher. Older versions may work, but we can't guarantee that.

1. Open a terminal and go to the project directory. For example:

   ```bash
   cd /home/user/myproject
   ```

1. Make sure Allure Report is installed. If it's not, follow the [installation instructions](/docs/v2/install/). Note that Allure Report requires Java.

1. Install the Allure Cucumber.js integration and make sure that all the packages it needs are installed.

   **npm:**
   ```bash
   npm install --save-dev @cucumber/cucumber @cucumber/messages allure-cucumberjs
   ```

   **yarn:**
   ```bash
   yarn add --dev @cucumber/cucumber @cucumber/messages allure-cucumberjs allure-js-commons
   ```

   **pnpm:**
   ```bash
   pnpm install --dev @cucumber/cucumber @cucumber/messages allure-cucumberjs
   ```

1. Enable the Allure formatter for Cucumber.js. See [Configuration](/docs/cucumberjs-configuration/) for more details and options.

   ```js
   export default {
     format: ["allure-cucumberjs/reporter"],
     formatOptions: {
       resultsDir: "allure-results",
     },
   };
   ```

   Warning:
   In Yarn PnP, the configuration will not work with the default settings. See [a note for Yarn PnP users](/docs/cucumberjs-configuration/#a-note-for-yarn-pnp-users).

1. Write your tests, following the official Cucumber.js documentation and, optionally, using some extended features provided by Allure Cucumber.js, see [Writing tests](#writing-tests).

### 2. Run tests

Run your Cucumber.js tests the same way as you would run them usually. For example:

**npm:**
```bash
npx cucumber-js
```

**yarn:**
```bash
yarn run cucumber-js
```

**pnpm:**
```bash
pnpx cucumber-js
```

This will save necessary data into `allure-results` or other directory, according to the [configuration](/docs/cucumberjs-configuration/). If the directory already exists, the new files will be added to the existing ones, so that a future report will be based on them all.

### 3. Generate a report

Finally, convert the test results into an HTML report. This can be done by one of two commands:

- `allure generate` processes the test results and saves an HTML report into the `allure-report` directory. To view the report, use the `allure open` command.

- `allure serve` creates the same report as `allure generate`, then automatically opens the main page of the report in a web browser.

## Writing tests

The Allure Cucumber.js integration extends the standard reporting features of Cucumber.js by providing additional capabilities for crafting more informative and structured tests. This section highlights key enhancements that can be utilized:

- **Metadata Annotation**: Enhance test reports with [descriptions, links, and other metadata](#add-metadata).
- **Test Organization**: Structure your tests into clear hierarchies for better readability and organization [organize tests](#organize-tests).
- **Step Division**: Break down tests into smaller [test steps](#divide-a-test-into-steps) for easier understanding and maintenance.
- **Parametrized Tests**: Clearly describe the parameters for [parametrized tests](#describe-parametrized-tests) to specify different scenarios.
- **Set labels globally**: Use [environment variables](#set-labels-globally) to set metadata and other labels.
- **Attachments**: Automatically capture [screenshots and other files](#attach-screenshots-and-other-files) during test execution.
- **Test Selection**: Use a test plan file to [select which tests to run](#select-tests-via-a-test-plan-file), allowing for flexible test execution.
- **Environment Details**: Include comprehensive [environment information](#environment-information) to accompany the test report.

In most cases, Allure Cucumber.js provides two different ways to use a feature: the Runtime API and the Gherkin tags.

- **Runtime API**: use Allure's functions to add certain data to the test result during its execution. This approach allows for constructing the data dynamically.

  Note that it is recommended to call the Allure's functions as close to the beginning of the test as possible. This way, the data will be added even if the test fails early.

- **Gherkin tags**: add a Gherkin tag of a specific format (may be configured via the [`labels`](/docs/cucumberjs-configuration/#labels) and [`links`](/docs/cucumberjs-configuration/#links) options). When using this approach, the data is guaranteed to be added regardless of how the test itself runs.

### Add Metadata

Allure allows you to enrich your reports with a variety of [metadata](/docs/v2/readability/#description-links-and-other-metadata). This additional information provides context and details for each test, enhancing the report's usefulness. Refer to the [metadata reference section](/docs/cucumberjs-reference/#metadata) for an exhaustive list of what can be added.

**Runtime API:**
```js
import { Then } from "@cucumber/cucumber";
import * as allure from "allure-js-commons";

Then("do something", async () => {
  await allure.owner("John Doe");
  await allure.severity("critical");
  await allure.tags("Web interface", "Authentication");
  // ...
});
```

**Gherkin tags:**
```gherkin
Feature: MyFeature

  @allure.label.owner:JohnDoe
  @allure.label.severity:critical
  @WebInterface
  @Authentication
  Scenario: MyTest
    When something should be done
    Then do something
```

### Organize tests

As described in [Improving navigation in your test report](/docs/v2/navigation/), Allure supports multiple ways to organize tests into hierarchical structures.

To specify a test's location in the [behavior-based hierarchy](/docs/v2/navigation/#behavior-based-hierarchy):

**Runtime API:**
```js
import { Then } from "@cucumber/cucumber";
import * as allure from "allure-js-commons";

Then("do something", async () => {
  await allure.epic("Web interface");
  await allure.feature("Essential features");
  await allure.story("Authentication");
  // ...
});
```

**Gherkin tags:**
```gherkin
Feature: MyFeature

  @allure.label.epic:WebInterface
  @allure.label.feature:EssentialFeatures
  @allure.label.story:Authentication
  Scenario: MyTest
    When something should be done
    Then do something
```

To specify a test's location in the [suite-based hierarchy](/docs/v2/navigation/#suite-based-hierarchy):

**Runtime API:**
```js
import { Then } from "@cucumber/cucumber";
import * as allure from "allure-js-commons";

Then("do something", async () => {
  await allure.parentSuite("Tests for web interface");
  await allure.suite("Tests for essential features");
  await allure.subSuite("Tests for authentication");
  // ...
});
```

**Gherkin tags:**
```gherkin
Feature: MyFeature

  @allure.label.parentSuite:TestsForWebInterface
  @allure.label.suite:TestsForEssentialFeatures
  @allure.label.subSuite:TestsForAuthentication
  Scenario: MyTest
    When something should be done
    Then do something
```

### Divide a test into steps

Allure Cucumber.js allows you to [create sub-steps](/docs/steps/) within a Gherkin test step. To do so, use the [`allure.step()`](/docs/cucumberjs-reference/#step) function.

Sub-steps are convenient for situations when you have a sequence of actions which is:

- monolithic enough to be presented as a single step in a Gherkin file;
- complex enough to have multiple potential points of failure.

```js
import { Then } from "@cucumber/cucumber";
import * as allure from "allure-js-commons";
import { Status } from "allure-js-commons";

Then("do something", async () => {
  await allure.step("Step 1", async () => {
    await allure.step("Sub-step 1", async (ctx) => {
      await ctx.parameter("foo", "1");
      // ...
    });
    await allure.step("Sub-step 2", async (ctx) => {
      await ctx.parameter("foo", "2");
      // ...
    });
  });
  await allure.logStep("Step 2", Status.SKIPPED);
});
```

### Describe parametrized tests

With Cucumber.js, you can implement the [parametrized tests](/docs/v2/readability/#parametrized-tests) pattern using the [`Scenario Outline` and `Examples` keywords](https://cucumber.io/docs/gherkin/reference#scenario-outline).

There are two approaches to indicate which parameters were used in a test:

- Use the angle brackets syntax to insert the parameter values directly into a step title.
- Use [`allure.parameter()`](/docs/cucumberjs-reference/#parametrized-tests) to display the values at the test level.

In the example below:

1. The `Examples` block defines two values for the `login` variable: “johndoe” and “johndoe\@example.com”.
2. For each value, Cucumber.js uses it instead of the placeholder in the scenario title and step titles, e.g., `authorize as "johndoe"`.
3. Cucumber.js then uses the title to select and run the JavaScript function. The value (e.g., “johndoe”) is passed to it as an argument of type `string`.
4. The function calls [`allure.parameter()`](/docs/cucumberjs-reference/#parametrized-tests) to display the values at the test level in the report.

```gherkin
Scenario Outline: test authorization as "<login>"
  Then authorize as "<login>"

  Examples:
    | login               |
    | johndoe             |
    | johndoe@example.com |
```

```js
import { Then } from "@cucumber/cucumber";
import * as allure from "allure-js-commons";

Then(`authorize as {string}`, async (login) => {
  await allure.parameter("auth_method", "password");
  await allure.parameter("login", login);
  // ...
});
```

### Set labels globally

Any [labels](/docs/cucumberjs-reference/#label), including custom ones, can be set via the environment variables in your operating system. Here's an example (assuming you use the `npm` package manager):

**MacOS/Linux:**
```bash
export ALLURE_LABEL_epic=WebInterface
npx cucumber-js
```

**Windows:**
```powershell
$Env:ALLURE_LABEL_epic = "WebInterface"
npx cucumber-js
```

### Attach screenshots and other files

In Allure reports, you have the ability to [attach various types of files](/docs/attachments/), which can greatly enhance the comprehensibility of the report. A common practice is to attach screenshots that capture the state of the user interface at specific moments during test execution.

For detailed instructions on how to implement attachments, refer to the [attachments section in the Allure Cucumber.js reference](/docs/cucumberjs-reference/#attachments).

```js
import { Then } from "@cucumber/cucumber";
import * as allure from "allure-js-commons";
import { ContentType } from "allure-js-commons";

Then("do something", async () => {
  // ...

  await allure.attachment("Text file", "This is the file content.", ContentType.TEXT);

  await allure.attachmentPath("Screenshot", "/path/to/image.png", {
    contentType: ContentType.PNG,
    fileExtension: "png",
  });
});
```

### Select tests via a test plan file

If the `ALLURE_TESTPLAN_PATH` environment variable is defined and points to an existing file, Cucumber.js will only run tests listed in this file.

Here's an example of running tests according to a file named `testplan.json` (assuming you use the `npm` package manager):

**MacOS/Linux:**
```bash
export ALLURE_TESTPLAN_PATH=testplan.json
npx cucumber-js
```

**Windows:**
```powershell
$Env:ALLURE_TESTPLAN_PATH = "testplan.json"
npx cucumber-js
```

### Environment information

For the main page of the report, you can collect various information about the environment in which the tests were executed. To do so, edit the [`environmentInfo`](/docs/cucumberjs-configuration/#environmentinfo) object in the configuration.

For example, it is a good idea to use this to remember the OS version and Node.js version retrieved from the [`os`](https://nodejs.org/api/os.html) and [`process`](https://nodejs.org/api/process.html) objects. This may help the future reader investigate bugs that are reproducible only in some environments.

Images: /images/js/environment-allure3.png, /images/js/environment-allure2.png

```js
import * as os from "node:os";
import * as process from "node:process";

export default {
  format: ["allure-cucumberjs/reporter"],
  formatOptions: {
    environmentInfo: {
      os_platform: os.platform(),
      os_release: os.release(),
      os_version: os.version(),
      node_version: process.version,
    },
  },
};
```

Note that if your launch includes multiple Cucumber.js runs (see [How it works](/docs/how-it-works/)), Allure Cucumber.js will only save the environment information from the latest run.