maintained by Qameta Software
Human-friendly test reporting for teams of any size.
Allure Report is an open-source, framework-agnostic test result visualization tool. It turns raw automated test output into clear, interactive reports that make quality visible across languages, frameworks, CI/CD systems, and teams.
The idea behind Allure is simple: test results should be readable by people, not just CI logs. Developers, QA engineers, managers, and stakeholders should all be able to understand what was tested, what failed, why it failed, and how quality changes over time.
And yes, after years of saying "for humans, not machines", it turns out structured, readable reports are pretty useful for AI agents too ;) Steps, labels, attachments, retries, history, environments, and failure context give agents enough signal to summarize test runs, spot patterns, and help teams act faster.
Website | Documentation | Live demo | Questions and Support | Announcements
Allure is not tied to one language, framework, or CI provider. The ecosystem is built around a shared result format and a set of tools that help teams collect, view, publish, and manage test results.
| Project | Use it for |
|---|---|
| Allure Report 3 | The next generation of Allure Report, rebuilt for modern quality workflows, dashboards, environments, history, and quality gates. See the Allure 3 docs. |
| Allure Report 2 | The stable, mature report generator with the broadest integration coverage. See the Allure 2 docs. |
| Allure integrations | Official libraries that turn test framework events into Allure result files. Start with the directory below. |
| Allure TestOps | A commercial quality platform for centralized test management, analytics, governance, and collaboration. |
Looking for the right repository? Start with the language-level integration. Framework-specific packages usually live there. The full framework index is available in the Allure documentation.
Repositories: allure-java, allure-kotlin, allure-gradle, allure-maven
Test frameworks and runners: JUnit 4, JUnit 4 AspectJ, JUnit 5, JUnit Platform, TestNG, Cucumber-JVM, JBehave 5, ScalaTest, Spock, Citrus, Karate
Kotlin and Android: Kotlin JUnit 4, AndroidX Test, Robolectric, and instrumentation tests
Browser and UI: Playwright Java, Selenide, Selenium BiDi
HTTP, API, and service clients: REST Assured, Apache HttpClient, Apache HttpClient 5, OkHttp, OkHttp 3, gRPC, JAX-RS, Servlet API, Spring Web
Assertions, data, and utilities: AssertJ, Hamcrest, JsonUnit, JUnit Jupiter assertions, Awaitility, jOOQ, JavaDoc descriptions
Repositories: allure-js, allure-npm
Docs and packages: Axios, AVA, Bun, Chai, CodeceptJS, Cucumber.js, Cypress, Fetch, Jasmine, Jest, Mocha, Newman, Node.js test runner, Playwright, TestCafe, Vitest, WebdriverIO
Repository: allure-python
Docs: Behave, Pytest, Pytest-BDD, Robot Framework
Repository: allure-csharp
Docs: NUnit, Reqnroll, SpecFlow, xUnit.net
Repositories: allure-php-commons2, allure-php-api, allure-phpunit, allure-codeception, allure-behat
Docs: Behat, Codeception, PHPUnit
Repository: allure-ruby
Docs: Cucumber.rb, RSpec
Docs: XCResults Reader
Repository: allure-go
Docs: Repository docs
Repository: allure-dart
Packages: Dart package:test, Flutter flutter_test and integration_test, Dart commons SDK
Repository: allure-rust
Docs and crates: Rust Cargo Test, Cargo test adapter, reqwest integration, Rust commons SDK, test macros
| Need | Links |
|---|---|
| GitHub Actions | allure-action, setup-allurectl, GitHub Action docs |
| Azure DevOps | Azure DevOps docs |
| Jenkins | Allure Jenkins plugin, Jenkins docs |
| Bamboo | allure-bamboo, Bamboo docs |
| TeamCity | allure-teamcity, TeamCity docs |
| IDEs | JetBrains IDEs, Visual Studio Code |
| Command line and packaging | allurectl, allure-npm, allure-debian |
| Demos | Allure 3 demo, Allure demo report |
Allure Report is Apache 2.0 open source and works locally, in CI, and in private environments.
When reporting alone is no longer enough, Allure TestOps turns the same Allure ecosystem into centralized, actionable quality management.
It helps teams move from isolated report artifacts to a living quality system with:
- Centralized storage and retention for test reports and quality evidence.
- Long-term launch history, analytics, trends, flaky-test visibility, and environment comparison.
- Actionable failure workflows: reruns, manual result decisions, resolution tracking, and defect creation.
- Unified automated and manual test management, with automated test cases kept in sync from real execution.
- Enterprise controls such as role-based access, team permissions, private projects, 2FA, SAML 2.0, OAuth 2.0, and deployment support.
For security and compliance details, see the Allure Trust Center.
- Ask usage questions in Questions and Support.
- Follow project news in Announcements.
- Share ideas in General Discussion.
- Open issues in the repository that owns the affected package or integration.
- Read the default contribution guide before opening a pull request.
- Report security vulnerabilities privately at security at qameta.io.
