[🐛 Bug]: Console.Logs not attaching to AllureReport on a failed cucumber step

[starbuck251]

Have you read the Contributing Guidelines on issues?

• I have read the Contributing Guidelines on issues.

WebdriverIO Version

7.10

Node.js Version

12

Mode

WDIO Testrunner

Which capabilities are you using?

NA

What happened?

When running tests with Cucumber framework, allure reporter and console.logs to be attached, when a step fails the logs are not attached to the allure report

I have chatted with @praveendvd on his PR #7134 around this issue
and a fix that was tested by my developer in house was confirmed along with Praveens initial thoughts on the fix. Fix just involves moving a single line to the top of onTestFail which is captured in the conversation on the PR.

What is your expected behavior?

On fail the logs should be attached to the allure report

How to reproduce the bug.

When running wdio with allure logs, cucumber framework, and console logs attaching to the allure report, when a step fails, on opening the report, the failed step does not have the logs leading up to failing, all passing steps contain logs.

Relevant log output

NA

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

[praveendvd]

Thank you will push the fix today 🙂

[praveendvd]

Fixed as part of #7691 , thanks for raising @starbuck251