Honor metadata label tags across Java test integrations - #1402
Merged
Merged
Conversation
pratushnyi
approved these changes
Aug 31, 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
allure.label.*framework tags are now converted into result labels before generated hierarchy defaults are applied. In Cucumber JVM, customparentSuite,suite, andsubSuitetags replace the automatic hierarchy instead of causing scenarios to appear twice in the Suite view.The convention now behaves consistently across Cucumber JVM 7, JUnit Platform, JUnit 4, TestNG, Spock 2, and Karate. Ordinary tags remain available, while metadata tags are consumed once so the report does not reapply them.
fixes #1030
Checklist