allure-framework / allure-framework/allure2
Single file report with history
- Dominant language
- HTML
- Stars
- 5.5k
- Forks
- 782
- Avg merge
- 2d 33m
- Merged PRs (30d)
- 16
Description
### Describe the Bug
Hello,
We upgraded to the latest version of Allure and tried to enable the new single file report feature.
Unfortunately, while the report works fine, it doesn't generate the "history" directory. As a result, it's not possible to accumulate results from previous runs while using single file reports, unless we also generate a multi file one to get the history directory.
Did we miss something here? Is it possible to get history in single file reports?
### Steps to Reproduce
1. Collect some test data
2. Generate single file report
3. Collect more test data
4. Generate new version of single file report
5. History from the previous report is not included
### Expected Behaviour
Single file reports should still generate the history data (optionally) so that it's possible to generate single file reports with history.
### Screenshots or Additional Context
(please disregard the "what language are you using" question reply, I cannot submit the issue without checking something, and Python and Robot Framework are not in the list)
### What Language are you using?
Android (Kotlin), C#, Go, Java, JavaScript, Kotlin, PHP, Ruby, TypeScript
### What Framework/Allure Integration you are using?
allure-robotframework
### What version of Allure Integration you are using?
2.13.5
### What version of Allure Report you are using?
2.30.0
### Code of Conduct
- [X] I agree to follow this project's Code of Conduct
Contributor guide
Research direction
Start by reproducing the reported sequence with Allure Report 2.30.0: generate two single-file reports from successive test-data collections and inspect whether history is preserved. Trace the single-file report generation entry point and compare it with multi-file generation, then verify that the second single-file report includes prior history without requiring a separate multi-file report.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- html
- Domain
- testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100