-
Notifications
You must be signed in to change notification settings - Fork 20
Plugin seems to break test.state property in cy.state('runnable') of a test suite #18
Comments
@proCrichard could you mention what plugin you are using? |
I wrote a custom plugin to send test results to datadog. Starts with an
Which triggers this event listener:
|
did your test that failed (but had state: passed) fail from a beforeEach hook or in the test body? What retry number do you have enabled? |
Retries set to 2
|
@proCrichard alright, and what version of cypress and this plugin? I just added your after() to my spec for this project, and I am getting the correct state set on the runnables |
|
@proCrichard ok, I think I am reproducing it now. Thanks |
Ok great. I appreciate you jumping on this for me. |
@proCrichard after spending a couple hours on this, I'll need to edit the Cypress source directly to fix this, but I have a PR to do so here cypress-io/cypress#3968 I would recommend using the module API to pull results out instead of using runnable instances. https://docs.cypress.io/guides/guides/module-api.html#cypress-run. However, I know that can be cumbersome |
When a test fails and is retried, that test's details in the
cy.state('runnable')
object is somehow broken. From an example I have here, I can see in the cypress logger that my test has failed:However the
cy.state('runnable')
output on that test considers it 'passed':This is throwing off a plugin I use to report test results. Any information you have on this issue would be helpful.
The text was updated successfully, but these errors were encountered: