Custom Chai Assertion Failures Show Failed Line in Test Instead of Support File

[Loren-Johnson]

What would you like?

In Open mode, when a custom Chai assertion fails, it shows the failure as coming from the support file (e.g e2e.ts) where the this.assert() call is. Ideally, this would show the line in the test that failed like it does for other assertions.

This example came from https://github.com/cypress-io/cypress-example-recipes/tree/master/examples/extending-cypress__chai-assertions where I changed line 67 of the spec file from

expect('foo').to.be.foo()

to

expect('foos').to.be.foo()

Why is this needed?

When one of these custom assertions fails, it can be difficult to determine what failed and where because the focus of the failure is shifted from a failed line in the test file to the assertion plumbing code in the support file.

Furthermore, if one wishes to override one of the existing chai assertions, such as .equals(), Cypress now reports ALL failures of that assertion as a failure in the support file rather than the test -- which reduces the value of such a customization.

Other

No response

[cypress-app-bot]

This issue has not had any activity in 180 days. Cypress evolves quickly and the reported behavior should be tested on the latest version of Cypress to verify the behavior is still occurring. It will be closed in 14 days if no updates are provided.

[Loren-Johnson]

Confirmed the issue is the same on Cypress 13.12.0

[cypress-app-bot]

This issue has not had any activity in 180 days. Cypress evolves quickly and the reported behavior should be tested on the latest version of Cypress to verify the behavior is still occurring. It will be closed in 14 days if no updates are provided.