Recommendations on the clean up rules

Created by George I., Modified on Wed, 05 Apr 2023 at 07:22 AM by George I.

Allure TestOps stores test runs artefacts aka test results files in a storage inside report container or on a dedicated S3 solution (which is much better).


Artefacts consume considerable amount of space, so you need to delete those on a regular basis.


Allure TestOps' built-in cleanup routine deletes the artefacts only for the closed launches, i.e. even if your rule states that files are to be deleted in 24 hours and a launch is in the open state, none of the artefacts of such launch will be deleted.



In Allure TestOps there are 3 types of artefacs (in order of decreasing storage consumption)
  1. attachments (consume most of the space), usually several per a test result
  2. fixtures (consume less than attachments), 
  3. scenario files (are supposed to be the smallest ones).

So when creating the cleanup rules you need to consider deleting all of artefacts described above.

There are separate rules for the deletion of the artefacts for test results with different status, e.g. for successful/failed tests.

For each result status you need to create 3 rules to delete each artefact type.

Hint: for successful tests (passed) it makes sense to keep 1-2 copies of the artefacts defined by the frequency of your tests runs, i.e. if your test runs 1 time per 24 hours, then it is reasonable to delete all the artifacts after, say 36 hours considering the information on the scheduler working (see the link above).

Rules to keep the artefacts for the other statuses depends on your team: you need to understand how much time is usually needed for the failures analysis and add some guard interval. 

Say, if you need 5 working days for the analysis, then delete the artefacts for failed tests after 168 hours (7 full days).


Example


This is not a recommendation but an example, what is the full list of cleanup rules is to be created for the artefacts clean-up.

The delay for the deletion should be defined by your internal processes.

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select atleast one of the reasons

Feedback sent

We appreciate your effort and will try to fix the article