-
-
Notifications
You must be signed in to change notification settings - Fork 2.7k
Closed
Labels
Bug 🐛good first picka reasonable task to start getting familiar with the code basea reasonable task to start getting familiar with the code basehelp wantedIssues that are free to take by anyone interestedIssues that are free to take by anyone interested
Description
Have you read the Contributing Guidelines on issues?
- I have read the Contributing Guidelines on issues.
WebdriverIO Version
8.5.6
Node.js Version
18
Mode
WDIO Testrunner
Which capabilities are you using?
"@wdio/allure-reporter": "^8.5.0"
"@wdio/mocha-framework": "^8.5.6",What happened?
It seems that the allure reporter creates a new step instead of a new entry in the "Retries" Tab (if a test fails and retries are configure in wdio).
I believe this also leads to unstable builds in jenkins.
In previuos version (wdio7 and corresponding allure reporter version) retries were listed in the "Retries" Tab and did not made jenkins unstable.
I attached some screenshots for comparison.



What is your expected behavior?
Retries are correctly listed in the retry tab and hopefully the publisher will not consider it as unstable anymore.
How to reproduce the bug.
Let a test fail and look into the generated allure report.
Relevant log output
n.a.Code of Conduct
- I agree to follow this project's Code of Conduct
Is there an existing issue for this?
- I have searched the existing issues
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
Bug 🐛good first picka reasonable task to start getting familiar with the code basea reasonable task to start getting familiar with the code basehelp wantedIssues that are free to take by anyone interestedIssues that are free to take by anyone interested