For anyone new to testing: I was so adamant to get really familiar with TDD, and working with testing-library has taught me that it's easier to test-drive a component once you have a few bigger tests in place. Many of us are using a third-party library for UI components, and in some cases there is a little discovery involved when asserting against the DOM that has been mangled by your library (looking at you, Semantic-UI-React select component). Once you've worked through a test like that, you'll know what to expect in the future, and that makes test-driving a bit more realistic.
Learning this library has changed the way I think about testing, too. 👍🏼
For anyone new to testing: I was so adamant to get really familiar with TDD, and working with testing-library has taught me that it's easier to test-drive a component once you have a few bigger tests in place. Many of us are using a third-party library for UI components, and in some cases there is a little discovery involved when asserting against the DOM that has been mangled by your library (looking at you, Semantic-UI-React select component). Once you've worked through a test like that, you'll know what to expect in the future, and that makes test-driving a bit more realistic.
Learning this library has changed the way I think about testing, too. 👍🏼
Awesome! I'm glad to hear others have had the same experience