Closed rmmanseau closed 1 year ago
I can look into this. This plugin takes the error created by DOM Testing Library to give more context to the error, but the stack trace isn't useful. Perhaps we can merge the message from DOM Testing Library and leave the rest of the assertion error alone.
If I replace the error message instead of the whole error, I can get what you want:
The top portion is the DOM Testing Library message while the Cypress error maintains Cypress context and stack traces.
:tada: This issue has been resolved in version 8.0.6 :tada:
The release is available on:
Your semantic-release bot :package::rocket:
first, to address this:
the getBy functions do work properly, but when they fail cypress is not able to figure out where the failure is coming from & point to it accurately. This makes for difficult debugging because it's not possible to immediately jump to the failed testing library commands. I believe that this issue does belong here, as the issue is specific to integration with cypress test runner.
cypress-testing-library
version: 8.0.3cypress
version: 10.10.0node
version: 14.20npm
(oryarn
) version: 1.22.19Relevant code or config
What you did:
run a test that fails on a cy.findBy* command
What happened:
it creates a
TestingLibraryElementError
and dumps the entire state of the DOMWhat I expected:
it generates an
Assertion Error
and points to the line of the failing assertion.Reproduction repository: https://github.com/rmmanseau/cy-testing-library-repro
Problem description:
@testing-library/cypress doesn't generate the correct assertion type / stack trace / whatever is required by cypress in order for it to point to the location of the failing line.
Suggested solution:
do the thing that cypress expects.