Allure Cypress configuration

The Allure Cypress adapter behavior can be affected by some configuration options set in your Cypress configuration file, e.g., cypress.config.ts.

The configuration options must be defined in the object passed to allureCypress() as the second argument. For example:

const { defineConfig } = require("cypress"); const { allureCypress } = require("allure-cypress/reporter"); module.exports = defineConfig({ e2e: { setupNodeEvents(on, config) { allureCypress(on, { resultsDir: "./allure-results", links: [ { type: "issue", urlTemplate: "" }, { type: "tms", urlTemplate: "" }, ], }); }, }, });


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

Patterns that can be used to construct full URLs from short identifiers, see the reference.

Each item of the links list must be an object with a type and a urlTemplate that will be used to construct URLs for the type. The template must include the %s placeholder. It will be replaced with the original short identifier.

For example, with the configuration above, allure.issue("AUTH-123") will produce a link leading to Allure will display the link with the appropriate icon for the issue type.

Powered by

Join our newsletter

Join our community

We aim to make Allure Report as reliable and user-friendly as possible, and together with the community, we're here to help when problems arise.

© 2024 Qameta Software Inc. All rights reserved.