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

Install Allure Report for Windows ​

Allure Report can be installed on Windows from the Scoop package repository or manually from an archive.

Install from Scoop ​

Allure Report commandline latest version

  1. Make sure Scoop is installed. See the installation instructions on GitHub.

  2. Make sure Java version 8 or above installed, and its directory is specified in the JAVA_HOME environment variable.

  3. In a terminal, run this command:

    scoop install allure
  4. Run this command to see if it reports the latest version:

    allure --version

Install from an archive ​

Allure Report commandline latest version

  1. Make sure Java version 8 or above installed, and its directory is specified in the JAVA_HOME environment variable.

  2. Go to the latest Allure Report release on GitHub and download the allure-*.zip or allure-*.tgz archive.

  3. Uncompress the archive into the directory of your choice.

    Remember the path to its bin subdirectory. You will need this path in a future step.

  4. Make sure that the allure command resolves to the allure file from your installation directory.

    There are various ways to do so, for example, via the Control Panel or by running a PowerShell script.

    Using Control Panel

    Details
    1. Press Win+R and enter the command: sysdm.cpl to open the System Properties tool.

    2. On the Advanced tab, click Environment variables.

    3. In either the User variables or System variables list, double-click the Path variable to open the editing dialog. Note that editing the system variable requires administrator privileges and affects all users of the computer.

    4. In the Edit environment variable dialog, click New to add a new line entry to the paths list. In the new line, specify the full path to the bin subdirectory from an earlier step, for example: D:\Tools\allure-2.29.0\bin.

    5. If the list contains a path to a previously installed Allure version, delete it.

    6. Click OK to save the changes.

    Using PowerShell

    Details
    1. Launch PowerShell and run the following three commands.

      (Replace D:\Tools\allure-2.29.0\bin with the path to the bin subdirectory from an earlier step.)

      powershell
      $AllureBinPath = "D:\Tools\allure-2.29.0\bin"
      $NewPath = (([Environment]::GetEnvironmentVariable("PATH", "User") -split ";") | ?{ $_ -and $_ -notlike "*\allure-*\bin" }) -join ";"
      [Environment]::SetEnvironmentVariable("PATH", "$NewPath;$AllureBinPath", "User")
    2. Close the current PowerShell window.

  5. In a new PowerShell window, run this command to see if it reports the latest version:

    allure --version
Pager
Previous pageInstall & Upgrade
Next pageInstall for macOS
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.