Boris Osipov

fix @qwez relesed in v5.13.0

>Is there any way I can have nested steps? No there is now way no.

@ybilevych feel free to propose PR, but before describe here how wdio-allure-reporter api will look like.

@kimek I would suggest you to think how implement it for v5 reporter version if you want this. This repo is obsolete and anyway we will ask to port any...

And againg it is not about wdio-reporter :) >I didn't managed to find any information. It is in allure docs. See https://docs.qameta.io/allure/#_links

>it appears to me that there should be somkind of API in reporter objet allowing set pattern. @baev can you assist? rigth now reporter just add `` to testcase. How...

@RickyMarou What exactly is "the same problem"? Default hook reporting behavior has not changed since webdriverio 4 to 8.

The root cause is `scenarioLevelReporter: true` https://github.com/ricalbuquerque/wdio-allure/blob/master/config/wdio.base.ts#L183 It breaks the normal cucumber reporter events order and break the allure and probably any similar reporter.

@ricalbuquerque The problem is in the custom `scenarioLevelReporter' wdio cucumber option which causes unexpected behaviour. It must be fixed in the wdio-cucumber adapter, but not in the allure reporter.

Seems like a failed test [here ](https://github.com/webdriverio/webdriverio/blob/main/packages/wdio-junit-reporter/src/index.ts#L135) and [here ](https://github.com/webdriverio/webdriverio/blob/main/packages/wdio-junit-reporter/src/index.ts#L213)is always marked as a failure, even if it was marked as an error before. Not sure when it was done...