search

systelab / allure-reporter

Printable report generation for Allure
4 stars 2 forks source link

Keep latest TC execution when finding a duplicate to be compatible with retries #115

Open Blackvals opened 11 months ago

Blackvals commented 11 months ago

Is your feature request related to a problem? Please describe. When a test framework like WDIO retries a test, you end up with 2 allure files for the same test; the one that failed and the retry that succeeded (flaky test). The AllureReporter currently handles duplicates by keeping the first that receives (i.e. 2 consecutive drag and drops keeps first, if both at the same time probably by alphabetic order of the name that is hash).

Describe the solution you'd like I would like to keep the latest, probably by looking into execution time inside the report not file properties

Describe alternatives you've considered There is no way to adjust allure file name from WDIO framework checking the libraries involved, by code inspection. It always generates a name with a random uuid at that time, thus not deterministic.

Additional context Change needs to be performed here: image

ManelMoreno commented 11 months ago

Decided to include this issue to v.4.0. Important: expected to show just the last execution time