#7104 wdio-junit-reporter - Mark test as skipped if on retry #7157
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Marking test as skipped in junit-reporter, and adding stacktrace if there is a failure
Proposed changes
This is meant to fix #7104
I did a little analysis in here, all the reporters behave the same, meaning if the test is retried is because it failed, so it will be marked as failed.
For junit, if a test is marked as failed (even tho it passed on the retry) then the whole suite is marked as failed.
So this PR is meant to fix that, it will mark the test as skipped and it will append the stack trace on the report.
Types of changes
Checklist
Further comments
Let's suppose we retry two times and passes on the second time.
Junit XML: Before changes
Junit XML: After
Reviewers: @webdriverio/project-committers