Skip to content
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

Closed
manuperez2 opened this issue Apr 15, 2021 · 7 comments · Fixed by #711
Closed

Retries not working with JUnit5 #710

manuperez2 opened this issue Apr 15, 2021 · 7 comments · Fixed by #711
Labels
type:bug Something isn't working

Comments

@manuperez2
Copy link

manuperez2 commented Apr 15, 2021

Describe the bug
Retries are not reflected in the report when executing with JUnit5 and Maven

To Reproduce
Steps to reproduce the behavior:

  1. Set the versions reflected below in pom.xml
  2. Configure surefire-plugin@3.0.0-M5 with 1
  3. Run a test failing and then succeeding (or failing, no matters)
  4. Generate the report
  5. Go to the Retries tab

Expected behavior
A retried run should appear

Screenshots
Test result:
image
Allure report:
image

Environment (please complete the following information):

Allure version 2.13.9
Test framework junit@5.7
Allure adaptor allure-junit5@2.13.9
Generate report using allure-maven@2.10.0

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

@manuperez2 manuperez2 added the type:bug Something isn't working label Apr 15, 2021
@vduhautois
Copy link

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.
And it's quite painful to lose retries management with junit 5 / maven

@vduhautois
Copy link

@baev Is there any chance of a fix on this ?

@baev
Copy link
Member

baev commented Dec 17, 2021

It would me much easier if you provided a reproducible example in form of GitHub repo

@zak-emobg
Copy link

Hi,

I'm experiencing the same issue with Allure 2.17.2.

@vduhautois
Copy link

vduhautois commented Feb 16, 2022

@baev
Sorry for the delay.
I've created this repo: https://github.com/vduhautois/AllureRetriesIssue
As written in the README, just run the test with

mvn clean test -Dtest=allure.AllureRetriesIssueTest#shouldGenerateAFlakyTest -Dsurefire.rerunFailingTestsCount=2

and it will do what you need to investigate.

Please let me know if you need anything else

@baev baev transferred this issue from allure-framework/allure2 Feb 16, 2022
@baev baev closed this as completed in #711 Feb 17, 2022
@rohanwolf
Copy link

@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!

@baev
Copy link
Member

baev commented Oct 31, 2024

@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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type:bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants