allure-framework / allure-framework/allure-python

Robot Framework Allure listener generates a huge amount of files

Open
#814 6 comments 10 reactions 0 assignees View on GitHub
Dominant language
Python
Stars
814
Forks
260
PR merge metrics
No merged PRs in 30d

Description

**Describe the bug**
When I use the Allure listener with Robot-Framework, a huge amount of files are generated.
For example : around 3000 json & html files (13MB !) are generated for a couple of basics Robot-Framework tests.
The final Allure report generated from the same tests also contains around 1500 files (6MB).

This situation has a limited impact for some basics tests, but, in case of my real tests campaign, more than 800.000 files are generated, for more than 1GB size ! This lead to memory issues or disk spaces failures.

**To Reproduce**
Steps to reproduce the behavior:
1. Start a basic Robot-Framework test campaign with the Allure listener ( --listener "allure_robotframework;allure-export"
2. Check the number of files in the "allure-export" folder and its size.
3. Generate the Allure report from the previous export files.
4. Check the number of files in the report folder, and its size .

**Expected behavior**
The listener output and Allure report should be optimized to reduce number of files generated and their size.

**Environment (please complete the following information):**

Allure version: 2.12.1
Test framework: robotframework@3.0.2
Allure adaptor: allure-robotframework@2.8.6

Contributor guide

Open the contributing guide

Research direction

Start by reproducing the issue with the named Robot Framework listener command and inspect the allure-export and generated report folders, comparing file counts and sizes. The payload names no source files or tests, so trace the listener and report-generation entry points from that reproduction; done means substantially fewer files and smaller output without losing report content.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
testing
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.