The JavaScript world moves pretty fast, and as we gain more experience using a framework our recommendations change. The is a good example of a framework that with deeper usage has eclipsed the alternatives to become the sensible default when testing React-based frontends. Our teams like the fact that tests written with this framework are less brittle than with alternative frameworks such as Enzyme, because you're encouraged to test component relationships individually as opposed to testing all implementation details. This mindset is brought by which React Testing Library is part of and which provides a whole family of libraries for Angular and Vue.js, for example.
The JavaScript world moves pretty fast, and as we gain more experience using a framework our recommendations change. The is a good example of a framework that with deeper usage has eclipsed the alternatives to become the sensible default when testing React-based frontends. Our teams like the fact that tests written with this framework are less brittle than with alternative frameworks such as Enzyme because you're encouraged to test component relationships individually as opposed to testing all implementation details.
As the pace of change in JavaScript frameworks has slowed, our teams have more time to work with specific frameworks and are gaining deeper insights as a result. With React and the dominant testing framework, Enzyme, we've observed a worrying trend of unit tests becoming tightly coupled to implementation details without providing ¡ª because the focus is on shallow details ¡ª much confidence that features work as expected. These unit tests make evolving the design difficult and they shift too much responsibility up the test pyramid to functional testing. This has made us revisit the idea of . Additionally, because of its design, trying to keep up with React's development. All this has pushed us toward assessing as a new framework for testing React applications.
