feat(nunit, xunit): set the default suites hierarchy for test results #578
Conversation
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
epszaw
approved these changes
Aug 13, 2025
This was referenced Dec 23, 2025
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
The PR implements the default suite hierarchy in Allure.NUnit and Allure.Xunit. See motivation in #364.
In NUnit, generic and parameterized classes are mapped to distinct sub suites.
If a test result already contains a suite hierarchy label (
parentSuite,suite, orsubSuite), the default labels are not added. This allows overwriting the default hierarchy with a custom one by using the Allure API (both runtime and attribute-based).Closes #364.