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
Chrome/Chroimum is not crashing, but the scenario fails with an AssertionError, which triggers the after each hook
We then see CypressError
CypressError: cy.task() must only be invoked from the spec file or support file.
Because this error occurred during a after each hook we are skipping the remaining tests in the current suite:
An error was thrown in your plugins file while executing the handler for the after:spec event.
The error we received was:
Error: Unexpected state in afterSpecHandler: step-started (this might be a bug, please report at https://github.com/badeball/cypress-cucumber-preprocessor)
Desired behavior
handle the unexpected state more gracefully, and allow any further scenarios in the feature file to continue
Current behavior
This is similar to this previous issue
Chrome/Chroimum is not crashing, but the scenario fails with an AssertionError, which triggers the after each hook
We then see CypressError
CypressError:
cy.task()
must only be invoked from the spec file or support file.Because this error occurred during a
after each
hook we are skipping the remaining tests in the current suite:An error was thrown in your plugins file while executing the handler for the after:spec event.
The error we received was:
Error: Unexpected state in afterSpecHandler: step-started (this might be a bug, please report at https://github.com/badeball/cypress-cucumber-preprocessor)
Desired behavior
handle the unexpected state more gracefully, and allow any further scenarios in the feature file to continue
Test code to reproduce
Versions
Checklist
cypress-cucumber-preprocessor@4.3.1
(package name has changed and it is no longer the most recent version, see #689).The text was updated successfully, but these errors were encountered: