On this page
Overview
Allure Report reads allure-results produced by test-framework adapters and renders test cases, steps, attachments, parameters, and history as interactive reports. It provides a common reporting format across many languages, testing frameworks, and CI/CD systems.
Features and best fit
Based on official documentation; not hands-on tested · Content checked:
Key features
Unify results from different test frameworks
Framework-specific Allure adapters emit a common results format, which Allure Report turns into HTML so suites written in different languages or runners can share a reporting model.
Sources: [1]
Expose steps, attachments, parameters, and execution history
Reports can go beyond pass/fail lists by preserving execution steps, screenshots or logs, parameters, and history that help diagnose failures.
Generate static reports for CI artifacts or hosting
allure generate converts a results directory into a static report directory suitable for CI artifacts or static hosting.
Sources: [3]
Best fit
Fits QA and development teams consolidating multi-language test reporting
It is useful when unit, API, and end-to-end suites use different frameworks but should be browsable through one report format by both developers and non-developers.
Sources: [1]
Before adoption
The report generator does not produce test results by itself
Allure Report consumes allure-results, so the test framework needs a compatible adapter configured to emit those files during execution.
Sources: [1]
allure serve is for local preview only
The command-line implementation explicitly scopes allure serve/open to ephemeral local review and directs hosted usage to allure generate followed by static serving.
Sources: [3]
Official sources
- [1]Allure Report README(2026-10-03)
- [2]Allure Report 2.46.1 release(2026-10-03)
- [3]Allure local report server implementation(2026-10-03)
- [4]Allure build configuration(2026-10-03)
- [5]Allure Report Apache-2.0 license(2026-10-03)
Supplemental curator note
Allure Report is useful when a project mixes languages or test frameworks but wants one reporting format in CI. The report generator does not create test results by itself—framework adapters do—and allure serve is intended only for local preview rather than shared hosting.
Try it in 3 steps
- 1
Install the Allure command line
This is the macOS/Homebrew path; use release assets or another official installation method on other systems.
brew install allure - 2
Generate results with the test-framework adapter
Configure the adapter for JUnit, pytest, Playwright, or the relevant framework so test execution writes allure-results.
Run your tests and create ./allure-results - 3
Preview the report locally
Review the report in the browser. For shared hosting, use allure generate to create static output instead of serve.
allure serve ./allure-results
Growth
Growth trends · Last 30 days
5,548 Stars
Trend data is still being collected.
Development activity
Last 90 days · weekly
- Commits (last 30 days)
- 4
- Open PRs
- 11
Development activity is still being collected.
Built with
Categories and tags
Categories
GitHub data
GitHub dataView detailed GitHub data
GitHub Topics
- allure
- reporting
- reporting-engine
- Stars
- 5,548
- Forks
- 783
- Watchers
- 139
- Open issues
- 77
- Contributors
- 89
- Owner type
- Organization
- Primary language
- HTML
- License
- Apache-2.0
- Repository last updated
- Oct 1, 2026
Related information
Write a related articleShare a guide or use case for this OSS in Markdown. Articles are published after administrator approval.
Explore next
- REST Assured7,139 Stars
2 shared tag(s) · 1 shared category(s)
test REST APIs from Java with a DSL for requests, status, headers, and JSON/XML assertions
Java - TestZeus Hercules1,174 Stars
2 shared tag(s) · 1 shared category(s)
turn Gherkin scenarios into LLM-agent browser actions for end-to-end testing
Python - Kestra29,012 Stars
2 shared tag(s)
orchestrate data, AI, and infrastructure workflows with one declarative model
Java - Argos636 Stars
1 shared tag(s) · 3 shared category(s)
review UI changes by comparing visual diffs for each pull request
TypeScript - Storybook91,196 Stars
1 shared tag(s) · 2 shared category(s)
capture UI states once and reuse them across docs, interaction tests, and agent tooling
TypeScript - Cypress51,043 Stars
1 shared tag(s) · 2 shared category(s)
run browser end-to-end and component tests through an interactive runner and CLI
TypeScript
Report incorrect information
Tell us if any listing information is incorrect or outdated.