Allure Framework
Allure Framework
Official Allure Framework projects, integrations, and community resources for test reporting.
- Learn more about Allure Report at https://allurereport.org
- 📚 Documentation – discover official documentation for Allure Report
- ❓ Questions and Support – get help from the team and community
- 📢 Official announcements – be in touch with the latest updates
- 💬 General Discussion – engage in casual conversations, share insights and ideas with the community
Overview
Allure Report is an open-source, framework-agnostic test result visualization tool. It turns automated test output into clear, interactive reports with steps, fixtures, attachments, labels, links, retries, history, environments, and failure details.
Allure was built to make test results readable by people rather than buried in CI logs. The plot twist is that the same structured evidence is useful for agents too: both humans and AI assistants can inspect a run, understand what failed, and decide what to do next.
Start Here
| Need | Start with |
|---|---|
| Learn what Allure Report shows | Allure Report docs, live demo |
| Generate a local report | Allure Report 3, Allure Report 2 |
| Add Allure to a test suite | Integration directory, full framework index |
| Publish reports in CI/CD | CI/CD and tooling |
| Centralize launches, analytics, and governance | Allure TestOps |
Ecosystem
| Project | Use it for |
|---|---|
| Allure Report 3 | Current-generation report UI, dashboards, environments, quality gates, and agent-friendly report data. |
| Allure Report 2 | Mature report generator with broad integration coverage and long-running ecosystem support. |
| Allure integrations | Language and framework adapters that write Allure result files from test runs. |
| Allure TestOps | Commercial quality platform for centralized test management, analytics, governance, and collaboration. |
Integration Directory
Most framework adapters live in a language-level repository. Expand a stack below or use the full framework index.
Java, Kotlin, Scala, Groovy, and JVM
- Repositories: allure-java, allure-kotlin, allure-gradle, allure-maven
- Test runners: JUnit 4, JUnit 4 AspectJ, JUnit 5, JUnit Platform, TestNG, Cucumber-JVM, JBehave 5, ScalaTest, Spock, Citrus, Karate
- UI, API, and clients: Playwright Java, Selenide, Selenium BiDi, REST Assured, Apache HttpClient, Apache HttpClient 5, OkHttp, OkHttp 3, gRPC, JAX-RS, Servlet API, Spring Web
- Utilities: AssertJ, Hamcrest, JsonUnit, JUnit Jupiter assertions, Awaitility, jOOQ, JavaDoc descriptions
JavaScript and TypeScript
- Repositories: allure-js, allure-npm
- Test runners and tools: AVA, Bun, CodeceptJS, Cucumber.js, Cypress, Jasmine, Jest, Mocha, Newman, Node.js test runner, Playwright, TestCafe, Vitest, WebdriverIO
- API and assertion helpers: Axios, Chai, Fetch
Python
- Repository: allure-python
- Integrations: Behave, Pytest, Pytest-BDD, Robot Framework
.NET
- Repository: allure-csharp
- Integrations: NUnit, Reqnroll, SpecFlow, xUnit.net
PHP
- Repositories: allure-php-commons2, allure-php-api, allure-phpunit, allure-codeception, allure-behat
- Integrations: Behat, Codeception, PHPUnit
Ruby
- Repository: allure-ruby
- Integrations: Cucumber.rb, RSpec
Apple and Xcode
- Integration: XCResults Reader
Go
- Repository: allure-go
- Docs: repository docs
Dart and Flutter
- Repository: allure-dart
- Packages: Dart package:test, Flutter flutter_test and integration_test, Dart commons SDK
Rust
- Repository: allure-rust
- Crates and docs: Rust Cargo Test, Cargo test adapter, reqwest integration, Rust commons SDK, test macros
CI/CD and Tooling
| 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 TestOps
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 ecosystem into centralized, actionable quality management for teams that need long-term storage, launch analytics, compliance, access control, and cross-project visibility.
For security and compliance details, see the Allure Trust Center.
Community
- 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.
- Report security vulnerabilities privately at security at qameta.io.