Add titlePath as the default test hierarchy path#1271
Merged
Merged
Conversation
pratushnyi
approved these changes
May 8, 2026
Allure Report Summary
|
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
This adds
titlePathto Allure Java results as a structured, unambiguous hierarchy path for tests. Unlike package-based grouping,titlePathis stored as an array of path segments, so names containing dots or other punctuation are preserved instead of being split unexpectedly.Allure Java integrations now populate
titlePathfrom the test framework’s natural structure: Java packages and classes for class-based tests, nested containers for JUnit Platform, XML suite/test context for TestNG, source file paths and feature/story names for BDD-style frameworks, and native suite/spec information for Spock, ScalaTest, and Citrus. Existing labels, names, full names, history IDs, and test case IDs remain unchanged for compatibility.For example, a Cucumber scenario in
features/simple.featurewith feature titleSimple featurewill now include a title path like["features", "simple.feature", "Simple feature"], allowing reports to build a clearer default tree without relying on label splitting.Checklist