Uncaught Exceptions should clearly indicate where they originated from

[brian-mann]

Currently when an uncaught exception causes a test to fail we only print the error.

This is confusing because Cypress fails the test for any kind of reason

• maybe there was an error in the test code itself
• maybe a command failed
• maybe your application threw an uncaught exception

In the cases of uncaught exceptions originating from your application we should CLEARLY indicate that is from your application code.

Bonus points for also doing the same thing when test code is the culprit.

[brian-mann]

Also we need a link to the Cypress Events to tell you how to turn this off

[jennifer-shehane]

Example of an error from my application under test. The actual stack trace is below a lot of messaging. I think most people see the error being thrown from cypress_runner.js and assume it's an error in cypress_runner.js

[brian-mann]

When there are uncaught exceptions from your application...

[brian-mann]

When there are uncaught exceptions from your test code...

[brian-mann]

Fixed by #999

[brian-mann]

Released in 1.1.3.

[sayedit09]

Hi,
Please help .i'm getting this error

[jennifer-shehane]

Hey @sayedit09, this error is coming from your application code - not Cypress. Click on the error with DevTools open and look at the stack trace to determine where this is being thrown in your application.