Use available Cucumber tag feature for Allure label instead of Feature name
#9727
Conversation
This file contains 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
christian-bromann
added
the
PR: Polish 💅
valfirst
deleted the
use-cucumber-tag-feature-for-allure-label-if-available-v7
branch
|
@christian-bromann would it be possible to release a new version that includes these changes? |
|
Sure, please stay tuned for that and watch the release tab. |
|
@christian-bromann thank you for 8.x release, would it be possible to release 7.x as well? |
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.
Backport of #9721.
Proposed changes
When Cucumber tag
featureis presented at scenario or feature level it should be used as Allure labelfeaturevalue for Allure test case (now it's always equal to CucumberFeaturename)Types of changes
Checklist
Further comments
Reviewers: @webdriverio/project-committers