Resolve cucumber's scenario outline template parameters

未关闭
#2,778 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
3/5
预计耗时
1-2 天
新手友好度
45/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
停滞
领域
testing

调研方向

issue 中没有指定源文件或测试。首先定位 scenario-outline 名称的渲染以及现有的模板参数处理,然后将其与此处显示的预期名称进行比较。完成标准是:生成的场景名称会将每个 outline 参数替换为相应的 Examples 值,并覆盖多个示例行。

由索引模型根据 Issue 内容生成。

描述

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 <start> cucumbers
  When I eat <eat> cucumbers
  Then I should have <left> cucumbers

  Examples:
    | start | eat | left |
    |    12 |   5 |    7 |
    |    20 |   5 |   15 |

to instead look like

Scenario Outline: Having <start> cucumbers, and eating <eat> leaves <left>
  Given there are <start> cucumbers
  When I eat <eat> cucumbers
  Then I should have <left> 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 <userType> <id> should have correct credentails.
and I get
User <userType> <id> 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
主要语言
JavaScript
星标
4.2k
派生
756
平均合并
2 天 9 小时
30 天内合并 PR
16

贡献指南

打开贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

codeceptjs/CodeceptJS 的其他 Issue

查看 codeceptjs/CodeceptJS 的全部 Issue

相似的 Issue

更多 JavaScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。