Uh oh!
There was an error while loading. Please reload this page.
Conversation
pratushnyi
approved these changes
Sep 4, 2026
Uh oh!
There was an error while loading. Please reload this page.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Context
Parameterized JUnit Jupiter tests that fail in
@BeforeEachnow retain their invocation parameters. A later successful attempt receives the same test case and history identity, allowing Allure Report and Allure TestOps to group the setup failure as a retry instead of displaying a separate result.Successful invocations continue to report their resolved argument values. Per-test setup failures remain attached to the real test invocation, while class- and container-level fixture failures continue to be reported as global errors without creating phantom tests.
fixes#1061
Checklist