Respect [AllureName] by titlePath of xUnit tests#660
Merged
Conversation
delatrie
force-pushed
the
titlePath-parameterized
branch
from
6b1c410 to
69ca472
Compare
epszaw
approved these changes
Jun 23, 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
The PR allows renaming the type node of a titlePath created via
CreateTitlePathby applying[AllureName(...)], which helps avoid non-user-friendly type names (such as types with generic parameters or nested types).Currently, this only affects xUnit.net, as Allure.NUnit uses NUnit-provided names for titlePath, and Allure.Reqnroll uses feature/scenario names.
Additionally, the PR adds a new
CreateTitlePathoverload that takes an instance ofMethodInfo. This overload also respects[AllureName]at the type and method levels.Checklist