Allow using "@" (at sign) in Gherkin step names#923
Closed
zenovich wants to merge 1 commit intoJetBrains:masterfrom
Closed
Allow using "@" (at sign) in Gherkin step names#923zenovich wants to merge 1 commit intoJetBrains:masterfrom
zenovich wants to merge 1 commit intoJetBrains:masterfrom
Conversation
Member
|
Hi @zenovich, thanks for your contribution. Is there a corresponding ticket in YouTrack? Also, what is the "custom syntax for variables in tests"? |
Contributor
Author
|
Hi @bartekpacia, |
bartekpacia
approved these changes
Jun 13, 2025
Member
bartekpacia
left a comment
bartekpacia
left a comment
There was a problem hiding this comment.
lgtm, started a merge request internally.
this PR will be closed automatically once it lands.
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.
This will allow steps like 'And @MyCustomGroup is a child of @ParentGroup' for those who use such custom syntax for variables in tests.
Note: It doesn't contradict Gherkin specifications as Gherkin tags (which have the similar syntax) are not allowed inside test steps.