BorisOsipov
commented
5 years ago Create issue in the v5 repo. Also create repo with reproduceable example. Will see what is the problem
On Sat, 19 Jan 2019, 13:09 Trey Turner <notifications@github.com wrote:
Since upgrading to wdio v5, most of my test runs conclude with the following output spammed to stderr:
[0-0] allure-js-commons: Unexpected endStep(). There are no any steps running
This happens anywhere from a few to several hundred times depending on the length of the spec/suite, inhibiting analysis of the spec reporter output. I'm sure this is the result of code running outside of tests, but this seems expected for setup and teardown, no?
The issue was raised in the allure-js-commons repo ( allure-framework/allure-js-commons#21 https://github.com/allure-framework/allure-js-commons/issues/21) but it was said that a fix would need to be found here.
I'm a little unclear as to the status of this reporter; it's still mentioned in the v5 docs, and I see it was moved to the new @wdio/* package namespace, but I also see that the code is in the boneyard. Thie reporter was useful to me and some of the non-engineering types in my org for v4, so it'd be great to have it as functional in v5.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/webdriverio-boneyard/wdio-allure-reporter/issues/150, or mute the thread https://github.com/notifications/unsubscribe-auth/AGNmZFhmLLZ20e0crdMrtyE6KPl9y0Lvks5vEu69gaJpZM4aJEO6 .
treyturner
Since upgrading to wdio v5, most of my test runs conclude with the following output spammed to stderr:
[0-0] allure-js-commons: Unexpected endStep(). There are no any steps runningThis happens anywhere from a few to several hundred times depending on the length of the spec/suite, inhibiting analysis of the spec reporter output. I'm sure this is the result of code running outside of tests, but this seems expected for setup and teardown, no?
The issue was raised in the
allure-js-commonsrepo (https://github.com/allure-framework/allure-js-commons/issues/21) but it was said that a fix would need to be found here.I'm a little unclear as to the status of this reporter; it's still mentioned in the v5 docs, and I see it was moved to the new
@wdio/*package namespace, but I also see that the code is in the boneyard. This reporter was useful to me and some of the non-engineering types in my org for v4, so it'd be great to have it as functional in v5.