You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In Gherkin it is possible to have scenario outlines with a parameterized name.
For example:
Feature: Examples Tables
Sometimes it can be desirable to run the same scenario multiple times with
different data each time - this can be done by placing an Examples table underneath
a Scenario, and use <placeholders> in the Scenario which match the table headers.
Scenario Outline: Eating <eat> cucumbersGiven there are <start> cucumbers
When I eat <eat> cucumbers
Then I should have <left> cucumbers
Examples: These are passing | start | eat | left | | 12 | 5 | 7 | | 20 | 8 | 12 | | 20 | 9 | 11 |
The pickles would then be named
Eating 5 cucumbers
Eating 8 cucumbers
Eating 9 cucumbers
✨ What's your proposed solution?
Add another, separate example with an example table that uses a parametrized scenario outline name.
When using a Scenario Outline it is possible to use a placeholder in the
name of that Scenario Outline. The resulting pickle will have the
placeholder replaced with a value from the example tables.
This allows us to test use cases where this matter such as:
- cucumber/junit-xml-formatter#34
- cucumber/testng-xml-formatter#4Fixes: #96
When using a Scenario Outline it is possible to use a placeholder in the
name of that Scenario Outline. The resulting pickle will have the
placeholder replaced with a value from the example tables.
This allows us to test use cases where this matter such as:
- cucumber/junit-xml-formatter#34
- cucumber/testng-xml-formatter#4Fixes: #96
🤔 What's the problem you're trying to solve?
In Gherkin it is possible to have scenario outlines with a parameterized name.
For example:
The pickles would then be named
✨ What's your proposed solution?
Add another, separate example with an example table that uses a parametrized scenario outline name.
📚 Any additional context?
This showed up with cucumber/junit-xml-formatter#27.
The text was updated successfully, but these errors were encountered: