-
Notifications
You must be signed in to change notification settings - Fork 227
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Retries not working with JUnit5 #710
Comments
I face the same issue. I stayed for a while with the 2.13.0 but too many CVE, I had to upgrade to the last version. |
@baev Is there any chance of a fix on this ? |
It would me much easier if you provided a reproducible example in form of GitHub repo |
Hi, I'm experiencing the same issue with Allure 2.17.2. |
@baev
and it will do what you need to investigate. Please let me know if you need anything else |
@baev Hi - is this same fix yet to be applied to allure-cucumber7-jvm? I am using this and I am getting the same uuid overriding issue. Only the latest execution of retry appears. Let me know please. Thanks! |
@rohanwolf please do not comment on the closed issues. Create a new discussion instead https://github.com/orgs/allure-framework/discussions/new?category=questions-support |
Describe the bug
Retries are not reflected in the report when executing with JUnit5 and Maven
To Reproduce
Steps to reproduce the behavior:
Expected behavior
A retried run should appear
Screenshots
Test result:
Allure report:
Environment (please complete the following information):
Additional context
It is working as expected with allure-junit5@2.13.0
Also, just the last run is displayed in the Timeline, as reported in allure-framework/allure2#1018
The text was updated successfully, but these errors were encountered: