Problem Statement
When running a Chainsaw test with multiple scenarios, it is currently difficult to tell which Scenario (and its associated bindings) is being executed at a given time. This makes debugging harder, since the logs and output only show the test name and step name, but not which Scenario is in progress.
Solution Description
The scenarios list could support a name property:
scenarios:
- name: scenario-name1
bindings:
- name: version
value: 2
- name: scenario-name2
bindings:
- name: version
value: 3
(Unfortunately, Chainsaw also does not support variable substitution in step name fields that could be a workaround to display the scenario in that field.)
It would be useful to allow optional naming of scenarios and display that scenario name (or index if unnamed) in the execution output, e.g.:
| 14:04:33 | test-name | scenario-name1 | step-name1 | TRY | BEGIN |
[...]
| 14:05:10 | test-name | scenario-name2 | step-name1 | TRY | BEGIN |
Alternatives
No response
Additional Context
No response
Slack discussion
No response
Research
Problem Statement
When running a Chainsaw test with multiple scenarios, it is currently difficult to tell which Scenario (and its associated bindings) is being executed at a given time. This makes debugging harder, since the logs and output only show the test name and step name, but not which Scenario is in progress.
Solution Description
The scenarios list could support a name property:
(Unfortunately, Chainsaw also does not support variable substitution in step name fields that could be a workaround to display the scenario in that field.)
It would be useful to allow optional naming of scenarios and display that scenario name (or index if unnamed) in the execution output, e.g.:
Alternatives
No response
Additional Context
No response
Slack discussion
No response
Research