allure-framework / allure2

Allure Report is a flexible, lightweight multi-language test reporting tool. It provides clear graphical reports and allows everyone involved in the development process to extract the maximum of information from the everyday testing process
https://allurereport.org/
Apache License 2.0
4.1k stars 703 forks source link

Single file report with history #2740

Open pulkomandy opened 5 days ago

pulkomandy commented 5 days ago

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

baev commented 4 days ago

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?

pulkomandy commented 4 days ago

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.