You want to write maintainable tests for your React Native components without testing implementation details, but then you're told to use Enzyme, which you learn has no React Native adapter, meaning only shallow rendering is supported. And you want to render deep! But deep rendering may otherwise require jsdom (React Native isn't the web!), while doing deep rendering with
react-test-renderer is so painful.
You would also like to use the newest React features, but you need to wait for your testing library's abstractions to catch up and it takes a while.
You finally want to approach testing using only best practices, while Enzyme may encourage assertions on implementation details.
react-native-testing-library is a lightweight solution for testing your React Native components. It provides light utility functions on top of
react-test-renderer letting you always be up to date with latest React features and write any component tests you like. It also prevents you from testing implementation details because we believe this is a very bad practice.
This library is a replacement for Enzyme.
You can find the source of
QuestionsBoard component and this example here.
Open a Terminal in your project's folder and run:
This library has a peerDependencies listing for
react-test-renderer and, of course,
react. Make sure to install them too!
As you may have noticed, it's not tied to React Native at all – you can safely use it in your React components if you feel like not interacting directly with DOM.
In order to properly use helpers for async tests (
findBy queries and
waitFor) you need at least React >=16.9.0 (featuring async
act) or React Native >=0.60 (which comes with React >=16.9.0).
Additional Jest matchers
In order to use addtional React Native-specific jest matchers from @testing-library/jest-native package add it to your project:
Then automatically add it to your jest tests by using
setupFilesAfterEnv option in your Jest configuration (it's usually located either in
"jest" key or in a