Single File Allure Report Has Larger File Size

[pandoras-toolbox]

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?

[baev]

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.

[pandoras-toolbox]

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.

[baev]

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.

[pandoras-toolbox]

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.