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
I have tests written in cypress. Calling npm test works perfectly. But then I defined a pre-commit hook with husky and it runs the tests but breaks in the end with TypeError: dest.end is not a function.
This made me think that the problem might actually be in cypress, so I decided to open this issue. One of my guesses is that since cypress does a lot of magic, including calling other executables, maybe it somehow messed up the "completion" of the script in a way that works for direct npm test but doesn't work when another library is trying to do something with the script output, error code or something like that.
Please take a look at the linked issue on husky for the full details, including the fully reproducible steps.
The text was updated successfully, but these errors were encountered:
interesting (and unexpected). Can you execute the commit hook with DEBUG=cypress* environment variable to see the debug logs?
jennifer-shehane
changed the title
Cypress tests breaks husky and pre-commit
Cypress tests breaks husky and pre-commit: TypeError: dest.end is not a function
Apr 24, 2019
I have tests written in cypress. Calling
npm test
works perfectly. But then I defined a pre-commit hook with husky and it runs the tests but breaks in the end withTypeError: dest.end is not a function
.At first I thought this was a problem with husky, not cypress, especially because running
npm test
directly works perfectly. So I opened an issue on husky about it, one month ago. But apparently this problem also occurs with a different git hooking library (namely pre-commit) as well.This made me think that the problem might actually be in cypress, so I decided to open this issue. One of my guesses is that since cypress does a lot of magic, including calling other executables, maybe it somehow messed up the "completion" of the script in a way that works for direct
npm test
but doesn't work when another library is trying to do something with the script output, error code or something like that.Please take a look at the linked issue on husky for the full details, including the fully reproducible steps.
The text was updated successfully, but these errors were encountered: