You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Similar to #2283, I'd like to propose implementing test:after:run as a plugin event, mirroring the driver event, specifically in the sense that it's invoked for skipped tests and that skipped-status can be detected.
Why is this needed?
I would like this in order to make "pretty output" of @badeball/cypress-cucumber-preprocessor to work better with skipped tests.
As explained in the docs, pretty output doesn't actually originate from the reporter, as reporters in Cypress are limited to Mocha events. Thus, most of pretty output originate from code running in setupNodeEvents() { .. }, IE. a plugin.
The plugin however is not aware of skipped tests (it.skip) and have no way of reporting them the way pretty output works with Cucumber JS, which is what the preprocessor tries to mimic.
Other
No response
The text was updated successfully, but these errors were encountered:
What would you like?
Similar to #2283, I'd like to propose implementing
test:after:run
as a plugin event, mirroring the driver event, specifically in the sense that it's invoked for skipped tests and that skipped-status can be detected.Why is this needed?
I would like this in order to make "pretty output" of
@badeball/cypress-cucumber-preprocessor
to work better with skipped tests.As explained in the docs, pretty output doesn't actually originate from the reporter, as reporters in Cypress are limited to Mocha events. Thus, most of pretty output originate from code running in
setupNodeEvents() { .. }
, IE. a plugin.The plugin however is not aware of skipped tests (
it.skip
) and have no way of reporting them the way pretty output works with Cucumber JS, which is what the preprocessor tries to mimic.Other
No response
The text was updated successfully, but these errors were encountered: