codeceptjs / codeceptjs/CodeceptJS

Resolve cucumber's scenario outline template parameters

Abierto
#2,778 0 comentarios 0 reacciones 0 asignados Ver en GitHub
Lenguaje dominante
JavaScript
Estrellas
4.2k
Forks
757
Merge medio
2 d 9 h
PR fusionados (30 d)
16

Descripción

#### 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

Guía de contribución

Abrir la guía de contribución

Evaluación

Este issue todavía no se ha evaluado.

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.