Details
-
Suggestion
-
Status: New
-
Resolution: Unresolved
-
None
-
None
-
None
Description
As system, Cucumber step's inline parameters must be ignored whenever added to the Automated Steps Library.
Thus,
Then the "assets/blank.scss" file should exist
is equivalent to:
Then the "./my-cool-theme-0.1.0.gem" file should exist
and should be stored as the following step in the library:
Then the "" file should exist
Notes:
- a step may contain one or more inline parameters
- there is no delimeter per Gherkin Reference (https://docs.cucumber.io/cucumber/step-definitions/#expressions) ; however it is quite common to have delimeters, such as double quotes, to clearly identify some argument
ACs:
- step must be persisted in the library without the values of the parameters
- in the administration settings, it shall be possible to define the possible parameter delimeters (" will be the default delimiter, but additional ones may be specified)
- whenever editing the stripped step within the library, it must update the corresponding Tests no matter what values they may be using for the parameters
References:
- https://docs.cucumber.io/gherkin/reference/#step-arguments
- projects with .features that can be used to validate this: https://docs.cucumber.io/community/projects-using-cucumber/
Attachments
Issue Links
- relates to
-
XRAY-3385 As system, Cucumber step's multiline arguments must be ignored whenever added to the Automated Steps Library
- New
-
XRAY-3383 As system, Cucumber step's placeholders for variables must be ignored whenever added to the Automated Steps Library
- New
-
XRAY-3509 As system, Cucumber expressions within steps must be supported
- New