Would you still need that if you’re using testing-library/react?
My guess is no, as you’re not dependent on enzyme. But, I’d have to stand up a test project or look at the testing-library repo
I switched from enzyme to testing-library about a year and half ago. I honestly don’t remember enzyme much already. I do enjoy testing library’s access methods.
I should take a look! I primarily stick with jest because the test suites behave and are constructed for front end and back end (node) code.
It’s still jest. It’s just an alternative for rendering components to enzyme. Yeah try it out!
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.
Would you still need that if you’re using testing-library/react?
My guess is no, as you’re not dependent on enzyme. But, I’d have to stand up a test project or look at the testing-library repo
I switched from enzyme to testing-library about a year and half ago. I honestly don’t remember enzyme much already. I do enjoy testing library’s access methods.
I should take a look! I primarily stick with jest because the test suites behave and are constructed for front end and back end (node) code.
It’s still jest. It’s just an alternative for rendering components to enzyme. Yeah try it out!