Allure Framework
Single File Allure Report Has Larger File Size #2854
-
|
It was a while ago, but when I tried out to create a single file Allure report it was around 50% larger compared to the non-single file Allure report. That adds up if these reports are archived. Of course it can be compressed, but even then a compressed non-single report is much smaller in size. Can the single file report perhaps be optimized so that it has the same file size or only slightly larger? |
Beta Was this translation helpful? Give feedback.
Replies: 5 comments 4 replies
-
|
All the report files are encoded in Base64, which is why the single-file report is larger. We can optimise it by removing base64 encoding for JSON/text files, but this will not significantly improve the situation in most cases. |
Beta Was this translation helpful? Give feedback.
-
|
Okay, thanks. If it is only slightly smaller its not worth doing it. 20% larger would be okay, but more would take too much space. Single-file is more nice-to-have, so it depends on the cost in a way. |
Beta Was this translation helpful? Give feedback.
-
|
Please feel free to check the size difference for the report with no attachments. That will give you a rough estimate of what we can optimise. The attachments have to have base64 encoding, and it may even double the size for some types of files. |
Beta Was this translation helpful? Give feedback.
-
|
We usually have a lot of attachments, images and JSON requests/responses. Most likely our attachments are the reason for the large file size so that the optimization for the other part would only reduce it for a small amount. Please forget about my request then, I think its not worth doing it for only a little less in file size. But maybe as an idea it can be documented that the file size is larger with single-file, so that users know its normal and expected. |
Beta Was this translation helpful? Give feedback.
-
|
@baev When the size of the generated single allure report file exceeds 500MB, the report cannot be viewed, allure reports loading forever; |
Beta Was this translation helpful? Give feedback.
-
|
The only limit is your hardware. Browsers may experience issues loading HTML pages larger than 500Mb. In Allure 3, we aim to optimise the single-file mode in various ways, but I doubt it will dramatically change things. |
Beta Was this translation helpful? Give feedback.
-
|
Multi-file mode can solve this problem. When I use the multi-file mode to generate a report, I need to start the allure server to view the report, which makes it impossible for me to send the report to the client to view it directly like the single-file mode. |
Beta Was this translation helpful? Give feedback.
-
|
500 MB per report is probably too much anyway. Why is it so much data? Because of screenshots? You can reduce them or take only screenshots if a test fails and if it is a UI test. If you attach JSON request and response strings you can abbreviate them if they are too long. I replaced the aspects which process the step annoations from Allure with a own implementation so that step parameter toString() values are automatically abbreviated if too long (would actually be nice if that was built into Allure that the maximum size of parameter toString() values is configurable). |
Beta Was this translation helpful? Give feedback.
-
|
Yes, because a lot of UI tests were run and there were a lot of failed screenshots and Parameters data |
Beta Was this translation helpful? Give feedback.
All the report files are encoded in Base64, which is why the single-file report is larger.
We can optimise it by removing base64 encoding for JSON/text files, but this will not significantly improve the situation in most cases.