We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
If you include a Variable in the Scenario outline it doesn't fill that variable in for the name of the test.
A feature file that includes a Scenario Outline and examples. And uses the examples in the Scenario Outline name.
Feature: Not supported yet Scenario Outline: Wow <name>-<birthyear> Given ... Then ... Examples: | name | birthyear | | Alice | 1985 | | Bob | 1975 |
Under the feature "Not supported yet" two test will appear named "Wow <name>-<birthyear>".
Wow <name>-<birthyear>
Two test would appear named: "Wow Alice-1985" & "Wow Bob-1975"
Wow Alice-1985
Wow Bob-1975
It does a better job of describing tests than example tags appearing to the right of the title.
The text was updated successfully, but these errors were encountered:
baace11
use native name for scenario outlines (fixes allure-framework#212 via a…
f4bdb75
…llure-framework#253)
d80225a
8e40d5f
No branches or pull requests
I'm submitting a ...
What is the current behavior?
If you include a Variable in the Scenario outline it doesn't fill that variable in for the name of the test.
Steps:
A feature file that includes a Scenario Outline and examples. And uses the examples in the Scenario Outline name.
Under the feature "Not supported yet" two test will appear named "
Wow <name>-<birthyear>
".What is the expected behavior?
Two test would appear named: "
Wow Alice-1985
" & "Wow Bob-1975
"What is the motivation / use case for changing the behavior?
It does a better job of describing tests than example tags appearing to the right of the title.
Please tell us about your environment:
The text was updated successfully, but these errors were encountered: