Fix JUnit Platform reporting for nested tests#1316
Merged
Conversation
baev
added
pr:improvement
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
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
JUnit Platform reports now preserve nested test class structure in suite labels, so nested Jupiter tests appear in the expected parent suite, suite, and sub-suite groups instead of being flattened under the innermost class. This keeps report navigation accurate for nested test hierarchies.
Nested classes with
@DisplayNameare also reflected consistently in suite labels and title paths. For example, a top-level display name such asA customer objectnow remains the parent grouping, while nested contexts likewhen createdandafter saving a customerappear as deeper report tree levels.fixes #1052
fixes #1234
Checklist