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

Azure DevOps integration ​

With the Allure Report plugin for Azure DevOps, you can set up automatic generation of reports after each test launch for your project.

1. Install the plugin ​

For the integration to work, you need to install the official Allure Report plugin to your Azure DevOps organization.

  1. On the Allure Report plugin page in the Visual Studio Marketplace, click Get it free.

  2. If prompted, sign in as your organization's administrator.

  3. Select your organization from the dropdown list. Click Install.

    Selecting organization for the plugin installation

2. Modify the pipeline ​

Once the plugin is installed, it makes the PublishAllureReport@1 task type available in Azure Pipelines. To enable building Allure Report for a pipeline, you will need to add a step with this task to it.

  1. Open the azure-pipelines.yml file in your repository. You can do it either in a local directory or in the Azure's web-based text editor.

  2. Add a step that uses the PublishAllureReport@1 task.

    Note that the step must be run later than any steps that can produce or modify your directory with test results. If you are unsure, add the new step to the very end of your pipeline.

  3. Optionally, specify additional parameters for the new step in its inputs section:

    • allureVersion — the version of Allure Report to use. See the Releases page on GitHub for the list of available versions. Defaults to 2.25.0, which is the earliest version supported by the Azure integration plugin.

    • testResultsDir — path to the current test results directory. Depending on the framework you use and the Allure adapter configuration, an appropriate path may be allure-results, build/allure-results, or some custom path.

  4. Save and commit the changes in the file. If you edited the file locally, don't forget to push the changes to the server.

Details

Here is an example of a pipelines file for a Java project.

yaml
steps:
  - script: ./gradlew clean test
    displayName: Run tests

  - task: PublishAllureReport@1
    displayName: Publish Report
    inputs:
      allureVersion: 2.27.0
      testResultsDir: allure-results

3. View test reports ​

After the configuration, each new job's page will include the Allure Report tab. The tab contains a frame with the test report.

Allure Azure DevOps plugin generate report

Pager
Previous pageIntegrations
Next pageBamboo
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.