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
If there's a failing expectation or exception in a fail handler, the error does not show the stack trace or a code frame with links to the calling code.
Desired behavior:
Such errors should display the stack trace and a code frame pointing to the call site.
Test code to reproduce
it('throws error in fail handler',()=>{cy.on('fail',()=>{foo.bar()// could also be a failed assertion})cy.get('#does-not-exist',{timeout: 1})})
Versions
Cypress 4.6.0+
The text was updated successfully, but these errors were encountered:
chrisbreiding
changed the title
Add better handling for errors thrown in fail handler
Errors thrown in fail handler don't show stack trace or code frame
May 28, 2020
The code for this is done in cypress-io/cypress#7513, but has yet to be released.
We'll update this issue and reference the changelog when it's released.
Current behavior:
If there's a failing expectation or exception in a
fail
handler, the error does not show the stack trace or a code frame with links to the calling code.Desired behavior:
Such errors should display the stack trace and a code frame pointing to the call site.
Test code to reproduce
Versions
Cypress 4.6.0+
The text was updated successfully, but these errors were encountered: