Scenario passed but event.test.failed emitted #4285
Unanswered
incoming-th
asked this question in
Q&A
Replies: 1 comment
-
|
I believe the event.test.failed is always triggered before each run, I tried to look at the object and all steps were passed, so this may not be the root cause. But I still don't understand why the interactive shell started just after Scenario 1 passed. I don't have pause() in the Scenario 2. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hi,
This is a bit of a complex situation and I am struggling for 3 days now so asking for help.
I have 1 suite with 2 scenarios that when running without -p pauseOnFail have no issue, but when using it the interactive shell started and Scenario 2 does not run, even if Scenario 1 passes.
I run in debug and verbose to get some clue and here is what I found, the event.test.failed seems to be triggered after Scenario 1 passed:
Running the above with DEBUG=codeceptjs:* npx codeceptjs run --steps -p pauseOnFail --verbose
Not quite sure what could be the cause, my quest so far could be that the use of pages + fragments + tryTo() may impact the event for false negative. Also again, running with only npx codeceptjs run works perfectly which is weird.
Thanks for any guidance on how to fix this.
Beta Was this translation helpful? Give feedback.
All reactions