CLI tool
allure-framework/allure2 avatar
allure-framework/allure2

Allure Report 2: a multi-language test report tool for teams that already have raw test results

Allure Report is a flexible, lightweight multi-language test reporting tool. It provides clear graphical reports and allows everyone involved in the development process to extract the maximum of information from the everyday testing process

5,585 stars781 forksHTMLApache-2.0

At a glance

What is it?
Allure Report 2 builds unified reports from dozens of testing tools into one browsable HTML report. It is a reporting layer, not a test runner, and that distinction decides whether it fits your stack.
Who is it for?
Adopt Allure Report 2 if your team already produces per-framework result files and wants one report across languages and CI systems, and if you accept that the CLI is a report generator rather than a test runner. Do not adopt it expecting it to schedule tests, manage environments or replace a test management platform: the README points to Allure TestOps for the platform role, and the command-line tool does not do that job.
Can I use it commercially?
Yes. Apache-2.0 is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
Is it still maintained?
Yes. The repository last received commits 2 days ago.
What is it written in?
Mainly HTML, according to GitHub's language statistics.

Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.

From daily snapshots

Star history

  • allure-framework/allure25,585 ★ · +42
Star history
Repository2026-09-232026-11-15
allure-framework/allure25.5k5.6k

42 Stars in the last 53 days, measured from the daily GitHub snapshot. Compare with other projects

Editorial analysis

What Allure Report 2 solves, and for whom

Test frameworks each ship their own output. JUnit writes XML, Jest writes JSON, and a project that runs more than one framework ends up with several unrelated result files and no single place to read them. Allure Report 2 exists to collapse that. The README describes it as a flexible multi-language test report tool that shows a detailed representation of what has been tested, and states that it can build unified reports for dozens of testing tools across eleven programming languages on several CI/CD systems. That is the whole pitch, and it is narrower than it sounds.

The tool is for teams that already run tests and already have raw results. If you are choosing a test runner, this is not it. Allure sits downstream: your framework executes, an adapter writes result files, and the Allure command line turns those files into an HTML report. The repository layout reflects this split. The top level contains allure-commandline, allure-generator, allure-plugin-api and a plugins directory, which is a report generator with an extension surface rather than a test execution engine. Anyone evaluating it as a replacement for their runner will be disappointed; anyone drowning in six kinds of result file will not.

How the Allure CLI turns framework output into an HTML report

The mechanism is a two-stage pipeline. First, a framework-specific adapter writes structured result files into a directory during test execution. Second, the Allure command line reads that directory and generates a static HTML report. The README does not spell out the directory name or the generator flags, so treat those as things to confirm in the documentation at allurereport.org/docs rather than assumptions.

The important architectural point is that the CLI is stateless with respect to your tests. It does not observe the run, hook into the process, or stream results. It reads files that already exist. That makes it easy to insert into an existing pipeline: run tests, then run the generator against the output directory. It also means the report is only as good as what the adapter recorded. If your adapter emits minimal data, the report will be minimal, and no amount of generator configuration will invent steps, attachments or severity levels that were never written.

The repository also exposes an allure-plugin-api and a plugins directory, which indicates the report generator is extensible rather than a fixed template. The README does not document what a plugin can change, so a team that needs custom report behaviour should read the plugin API source before assuming the extension point covers their case.

Installing the Allure command line and generating a first report

The README gives three distribution routes: release assets on GitHub, Homebrew, and Scoop on Windows. It does not give a Linux package manager command, and it does not give a Docker image, so plan for the release archive on Linux agents.

On macOS or Linux with Homebrew, the README's command is a single line:

bash
brew install allure

On Windows, the README directs you to install Scoop first and then run:

bash
scoop install allure

After installation, the CLI is on your PATH. The README does not document the generation command, so the exact invocation (the results directory argument and the output directory argument) has to come from the official documentation rather than from this page. What the README does confirm is the shape of the workflow: your test framework writes result files, and the CLI converts them into a browsable report. The live demo at demo.allurereport.org shows what the generated report looks like once you have one.

For a first real use, pick a single test module, run it with an Allure adapter enabled, confirm the result files appear on disk, then point the CLI at that directory. If the result directory stays empty, the problem is on the adapter side, not the CLI side, and that is the fastest way to localise a broken setup.

Where Allure Report 2 is the wrong tool

The README is explicit that Allure TestOps is a separate product, described as a DevOps-ready testing platform, and it is marketed separately by Qameta Software. That sentence draws a boundary. Allure Report 2 generates and displays reports. It does not store history across runs in a queryable database, it does not manage test cases, and it does not assign or track defects. Teams that need flaky-test tracking over time, manual test case management, or a shared web service for many projects are looking at the platform, not at this repository.

There is a second limitation that follows from the architecture. Because the CLI reads files rather than instrumenting the run, anything that happens outside the adapter's recording is invisible. A retry that the framework handles internally, a fixture that silently swallows an exception, a parallel worker that dies before writing its file: none of that necessarily surfaces in the report. The report reflects the adapter's output, and the adapter's output reflects a particular framework's idea of what a test result is. Cross-framework unification is a genuine benefit, but it is a lowest-common-denominator unification in places.

Finally, the project is a report generator with a Java-based commandline distribution. The README does not state runtime requirements, so a team with locked-down CI images should verify the Java requirement before standardising on it.

Allure Report 2 versus a framework's built-in HTML reporter

The most obvious alternative is the HTML reporter that ships with your test framework. The difference in approach is scope. A built-in reporter knows one framework deeply and formats that framework's native result model. Allure normalises many frameworks into a shared model and renders that.

If your project runs a single framework and one language, the built-in reporter is usually less work and produces a report with no translation layer. Allure starts paying off when you have more than one framework or more than one language in the same pipeline, because the alternative is stitching several unrelated HTML files together by hand. The README claims support for dozens of testing tools across eleven languages, which is the case where the normalisation cost buys something.

The other alternative is a hosted test analytics platform, including Allure TestOps itself. Those store results over time and answer questions like whether a test has been flaky for three weeks. Allure Report 2 answers what happened in this run. That is a smaller question, and it is answered without standing up a service.

Maintenance, releases and what the Apache-2.0 licence means here

The repository is not archived, and the last push was on 2026-11-02. Recent releases are 2.46.1 on 2026-09-03, 2.46.0 on 2026-08-28 and 2.45.0 on 2026-08-06, so the release cadence is roughly monthly. The README does not document a support policy for older minor versions, and it does not document a rollback procedure for the CLI itself, so pinning a version in CI is the practical way to keep report output stable across pipeline runs.

Upgrade cost is mostly the adapter side. The command line and the framework adapters are separate artifacts, and the README does not describe a compatibility matrix between them. A CLI upgrade that changes report rendering is low risk; an adapter upgrade that changes the result file format is the one to watch, and the README does not say which releases did that.

The project is licensed under Apache-2.0, which is a permissive licence that generally allows commercial use and modification with attribution and notice requirements. The README links to the licence text but does not summarise obligations. Whether your redistribution of a generated report or a modified build triggers notice requirements is a question for your own legal review, not something this page can settle.

Editorial conclusion

Adopt Allure Report 2 if your team already produces per-framework result files and wants one report across languages and CI systems, and if you accept that the CLI is a report generator rather than a test runner. Do not adopt it expecting it to schedule tests, manage environments or replace a test management platform: the README points to Allure TestOps for the platform role, and the command-line tool does not do that job. Before committing, verify three things against your own setup: that your test framework has an Allure adapter and writes the result directory the CLI expects, that the Java runtime available on your CI agents satisfies what the commandline distribution requires, and whether you can pin the CLI version so report output does not shift under you between pipeline runs.

Frequently asked questions

What is Allure Report 2 used for?

It builds unified test reports from the output of many testing tools across multiple languages and CI/CD systems, then renders them as an HTML report. It is a reporting layer that sits after test execution, not a test runner.

How do I install the Allure command line?

The README gives three routes: download the release assets from GitHub, run brew install allure on macOS or Linux with Homebrew, or install Scoop on Windows and run scoop install allure.

What is Allure Report and what does it do?

According to the README, it is a flexible multi-language test report tool that shows a detailed representation of what has been tested. It reads result files written by framework adapters and generates a graphical HTML report.

How can I view an Allure report?

The CLI generates a static HTML report from the result directory, which you then open in a browser. The README also points to a live demo at demo.allurereport.org, though the README does not document the exact generation command.

Official sources

  1. allure-framework/allure2 on GitHub
  2. License: Apache-2.0
  3. Project website
  4. README
  5. Releases
Add this badge to your README

If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.

Add this badge to your README

markdown
[![Hysen Labs](https://hysenlabs.com/badge/allure-framework-allure2.svg)](https://hysenlabs.com/projects/allure-framework-allure2)

Star history chart for your README

markdown
[![Star history](https://hysenlabs.com/chart/allure-framework-allure2.svg)](https://hysenlabs.com/projects/allure-framework-allure2)

Was this useful?