React Native Testing Library
Simple and complete React Native testing utilities that encourage good testing practices.
[![Version][version-badge]][package]
[![PRs Welcome][prs-welcome-badge]][prs-welcome]
[![Chat][chat-badge]][chat]
[![codecov][codecov-badge]][codecov]
[![Sponsored by Callstack][callstack-badge]][callstack]
## The problem
You want to write maintainable tests for your React Native components. As a part of this goal, you want your tests to avoid including implementation details of your components and rather focus on making your tests give you the confidence for which they are intended. As part of this, you want your testbase to be maintainable in the long run so refactors of your components (changes to implementation but not functionality) don't break your tests and slow you and your team down.
## This solution
The React Native Testing Library (RNTL) is a lightweight solution for testing React Native components. It provides light utility functions on top of `react-test-renderer`, in a way that encourages better testing practices. Its primary guiding principle is:
> The more your tests resemble the way your software is used, the more confidence they can give you.
This project is inspired by [React Testing Library](https://github.com/testing-library/react-testing-library). Tested to work with Jest, but it should work with other test runners as well.
## Installation
Open a Terminal in your project's folder and run:
#### Using `yarn`
```sh
yarn add --dev @testing-library/react-native
```
#### Using `npm`
```sh
npm install --save-dev @testing-library/react-native
```
This library has a peerDependencies listing for `react-test-renderer` and, of course, `react`. Make sure to install them too!
> 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.61 (which comes with React >=16.9.0).
### Additional Jest matchers
In order to use additional React Native-specific jest matchers from [@testing-library/jest-native](https://github.com/testing-library/jest-native) package add it to your project:
#### Using `yarn`
```sh
yarn add --dev @testing-library/jest-native
```
#### Using `npm`
```sh
npm install --save-dev @testing-library/jest-native
```
Then automatically add it to your jest tests by using `setupFilesAfterEnv` option in your Jest configuration (it's usually located either in `package.json` under `"jest"` key or in a `jest.config.json` file):
```json
{
"preset": "react-native",
"setupFilesAfterEnv": ["@testing-library/jest-native/extend-expect"]
}
```
### Custom Jest Preset (React Native before 0.71)
We generally advise to use the "react-native" preset when testing with this library.
However, if you use React Native version earlier than 0.71 with [modern Jest fake timers](https://jestjs.io/blog/2020/05/05/jest-26#new-fake-timers) (default since Jest 27), you'll need to apply this custom Jest preset or otherwise awaiting promises, like using `waitFor` or `findBy*`, queries will fail with timeout.
This is a [known issue](https://github.com/facebook/react-native/issues/29303). It happens because React Native's Jest preset overrides native Promise. Our preset restores it to defaults, which is not a problem in most apps out there.
Here's how you apply a custom preset in your Jest config:
```json
{
"preset": "@testing-library/react-native"
}
```
If this doesn't work for you, please fall back to using "legacy" fake timers.
### Flow
Note for [Flow](https://flow.org) users – you'll also need to install typings for `react-test-renderer`:
```sh
flow-typed install react-test-renderer
```
## Example
```jsx
import { render, screen, fireEvent } from '@testing-library/react-native';
import { QuestionsBoard } from '../QuestionsBoard';
test('form submits two answers', () => {
const allQuestions = ['q1', 'q2'];
const mockFn = jest.fn();
render(