Skip to content

[🐛 Bug]: cucumberOpts.retry is not properly labeled in the spec reporter #13879

@christian-bromann

Description

@christian-bromann

Have you read the Contributing Guidelines on issues?

WebdriverIO Version

latest

Node.js Version

latest

Mode

WDIO Testrunner

Which capabilities are you using?

any

What happened?

If you set the retry option in the cucumberOpts and your scenario fails, Cucumber properly retries the scenario, however the spec reporter (maybe others) don't mark it as such. In fact it returns with the following confusing result:

[chrome 132.0.6834.0 mac #0-0]
[chrome 132.0.6834.0 mac #0-0] 77 passing (51.5s)
[chrome 132.0.6834.0 mac #0-0] 1 failing


Spec Files:      1 passed, 1 total (100% completed) in 00:00:55

What is your expected behavior?

Behave similar to Mocha.

How to reproduce the bug.

n/a

Relevant log output

n/a

Code of Conduct

  • I agree to follow this project's Code of Conduct

Is there an existing issue for this?

  • I have searched the existing issues

Metadata

Metadata

Labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions