I like Jest but it quickly becomes a mess when introducing Typescript, and testing backend code.
Mocking named exports is a big mess.
Other than that I like Jest (except for their ties to Facebook evil )
Great article, good for introduction, thanks
Thanks for leaving a comment :) Yea... It needs a lot of workarounds when it comes to Typescript :)
It does - but I still use Jest as for me its the best all around unit testing framework/library.
For E2E and integration tests, I swear on Cypress, but Jest rules for unit tests.
Cheers, and thanks
Some comments have been hidden by the post's author - find out more
Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink.
Hide child comments as well
Confirm
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I like Jest but it quickly becomes a mess when introducing Typescript, and testing backend code.
Mocking named exports is a big mess.
Other than that I like Jest (except for their ties to Facebook evil )
Great article, good for introduction, thanks
Thanks for leaving a comment :)
Yea... It needs a lot of workarounds when it comes to Typescript :)
It does - but I still use Jest as for me its the best all around unit testing framework/library.
For E2E and integration tests, I swear on Cypress, but Jest rules for unit tests.
Cheers, and thanks