codeceptjs / codeceptjs/CodeceptJS

in BDD or Gherkin mode, the `After` is not synchronous where next scenario starts (while the `After` is still executing)

未关闭
#4,288 9 条评论 1 个 reaction 已指派 0 人 在 GitHub 查看
stale
主要语言
JavaScript
星标
4.2k
派生
757
平均合并
2 天 9 小时
30 天内合并 PR
16

描述

#### What are you trying to achieve?
In BDD / Gherkin mode, [After](https://codecept.io/bdd/#after) to be synchronous so it run to completion before the next scenario starts

Scenario 1
After --- run completely before Scenario 2 start
Scenario 2

#### What do you get instead?
`After` is asynchronous so it might still running while the next scenario already starting
It seems that the `After` implementation is based on [event](https://github.com/codeceptjs/CodeceptJS/blob/3.x/lib/container.js#L320-L322) which is independent from the promise chain.

### Details

* CodeceptJS version: 3.5.13
* NodeJS Version: v18.19.0
* Operating System: macOS
* webdriverio 8.32.0

贡献指南

打开贡献指南

评估

这个 Issue 还没有评估数据。

把新 issue 发到你的邮箱

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