Repository navigation
Improve JUnit Platform and Jupiter reporting - #1315
Merged
Merged
Conversation
pratushnyi
approved these changes
Jul 9, 2026
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 free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
Allure reports for JUnit Platform and Jupiter now capture more of the test execution shape users expect to see. Jupiter lifecycle methods are reported as fixtures on the correct scope, including failed setup methods, and parameterized class invocations now produce distinct, readable test results.
Parameterized Jupiter tests also get richer parameter reporting, including
@Parammetadata, class-level arguments, and nested template arguments without duplication. JUnit Platform published files are attached to the current test result, so artifacts emitted throughTestReporter.publishFileare available directly in the report.Checklist