codeceptjs / codeceptjs/CodeceptJS

Resolve cucumber's scenario outline template parameters

Aperta
#2,778 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub
Lingua principale
JavaScript
Stelle
4.2k
Fork
757
Merge medio
2g 9h
PR unite (30g)
16

Descrizione

#### What are you trying to achieve?
When using cucumber's scenario outlines, it's much easier to review your tests results when they don't all have the same name.
So cucumber supports converting the following

```
Scenario Outline: eating
Given there are cucumbers
When I eat cucumbers
Then I should have cucumbers

Examples:
| start | eat | left |
| 12 | 5 | 7 |
| 20 | 5 | 15 |
```
to instead look like
```
Scenario Outline: Having cucumbers, and eating leaves
Given there are cucumbers
When I eat cucumbers
Then I should have cucumbers

Examples:
| start | eat | left |
| 12 | 5 | 7 |
| 20 | 5 | 15 |
```
It was done here https://github.com/cucumber/cucumber-js/issues/267
The 2nd version of this test would produce scenarios with the following names:
- Having 12 cucumbers, and eating 5 leaves 7
- Having 20 cucumbers, and eating 5 leaves 15

#### What do you get instead?
Instead, it appears the template parameters are not resolved when printing the scenario name when the feature is run

> Provide console output if related. Use `--verbose` mode for more details.
In my case my scenario name is `User should have correct credentails.`
and I get
` User should have correct credentails. {"userType":"\"issuer_rep\"","id":"10","homePage":"\"landing/info\""}`

### Details
* CodeceptJS version: CodeceptJS v3.0.4
* NodeJS Version: v14.2.0
* Operating System: Windows/Mac/Ubuntu
* webdriverio

Guida per i contributori

Apri la guida per i contributori

Valutazione

Questa issue non è ancora stata valutata.

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.