Conversation
Allure Report Summary
Reports: Awesome Artifacts used (50)
|
pratushnyi
approved these changes
Sep 25, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Context
Allure 2 now generates a root
summary.jsonin both directory and single-file modes, using the common Allure 3 summary format. CI integrations such as Jenkins can use it to read test counts, status, and timing without reconstructing statistics from raw results.Single-file reports now write
history/and integration exports besideindex.html. Carrying that history into the next build preserves test history and trends without generating a separate multi-file report. The HTML remains self-contained, including widgets, attachments, and CSV downloads.fixes #2740
Checklist