Single file report with history
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
- Collect some test data
- Generate single file report
- Collect more test data
- Generate new version of single file report
- 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
Do you have any ideas on how this should be implemented, by chance? Do you expect Allure to generate a history folder together with index.html for the single file mode?
I think that would work for us.
Another option would be to extract the history info from the single file index.html, but that seems more complex to do.
For now we will continue using multiple file reports. That's fine for us, but at least the documentation should mention this limitation then.
Is there any workaround to solve it temporarily?
any updates?
The feature is already supported in Allure 3 https://github.com/allure-framework/allure3
As for today, there are no plans to support it in Allure 2, but at some point we may consider backporting it
@baev - can you give an example/point to documentation for how to accomplish this in allure3? I didn't see anything obvious in the README