_Appreciation notice: This project is heavily inspired by [react-testing-library](https://github.com/kentcdodds/react-testing-library). Go check it out and use it to test your web React apps._
You want to write maintainable tests for your React Native components without testing implementation details, but then you're told to use Enzyme, which only supports shallow rendering in React Native environment. And you want to render deep! But doing so 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.
## This solution
The `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, be it shallow or deeply rendered ones. But really not any, it prevents you from testing implementation details because we stand this is a very bad practice.
This library is a replacement for [Enzyme](http://airbnb.io/enzyme/).
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.
/* You won't often use this, but it's helpful when testing refs */
createNodeMock:(element:React.Element<*>)=>any,
}
):RenderResult{}
```
Deeply render given React element and returns helpers to query the output. For convenience it also returns `react-test-renderer`'s `instance` and `renderer` objects, in case you need more control.
Returns a `RenderResult` object with following properties:
### `getByTestId: (testID: string)`
A method returning a `ReactTestInstance` with matching `testID` prop. Throws when no matches.
_Note: most methods like this one return a [`ReactTestInstance`](https://reactjs.org/docs/test-renderer.html#testinstance) with following properties that you may be interested in:_
A method returning an array of `ReactTestInstance`s with matching name – may be a string or React Element.
### `getByText: (text: string | RegExp)`
A method returning a `ReactTestInstance` with matching text – may be a string or regular expression. Throws when no matches.
### `getAllByText: (text: string | RegExp)`
A method returning an array of `ReactTestInstance`s with matching text – may be a string or regular expression.
### `getByProps: (props: { [propName: string]: any })`
A method returning a `ReactTestInstance` with matching props object. Throws when no matches.
### `getAllByProps: (props: { [propName: string]: any })`
A method returning an array of `ReactTestInstance`s with matching props object.
### `update: (element: React.Element<*>) => void`
Re-render the in-memory tree with a new root element. This simulates a React update at the root. If the new element has the same type and key as the previous element, the tree will be updated; otherwise, it will re-mount a new tree.
### `unmount: () => void`
Unmount the in-memory tree, triggering the appropriate lifecycle events
When using React context providers, like Redux Provider, you'll likely want to wrap rendered component with them. In such cases it's convenient to create your custom `render` method. [Follow this great guide on how to set this up](https://github.com/kentcdodds/react-testing-library#custom-render).
Shallowly render given React component. Since it doesn't return helpers to query the output, it's mostly advised to used for snapshot testing (short snapshots are best for code reviewers).
Wait for non-deterministic periods of time until your element appears or times out. `waitForExpect` periodically calls `expectation` every `interval` milliseconds to determine whether the element appeared or not.
If you're using Jest's [Timer Mocks](https://jestjs.io/docs/en/timer-mocks#docsNav), remember not to use `async/await` syntax as it will stall your tests.
Each of the get APIs listed in the render section above have a complimentary query API. The get APIs will throw errors if a proper node cannot be found. This is normally the desired effect. However, if you want to make an assertion that an element is not present in the hierarchy, then you can use the query API instead:
```jsx
import{render}from'react-native-testing-library';
const{queryByText}=render(<Form/>);
constsubmitButton=queryByText('submit');
expect(submitButton).toBeNull();// it doesn't exist
```
## `queryAll` APIs
Each of the query APIs have a corresponding queryAll version that always returns an Array of matching nodes. getAll is the same but throws when the array has a length of 0.
```jsx
import{render}from'react-native-testing-library';
const{queryAllByText}=render(<Forms/>);
constsubmitButtons=queryAllByText('submit');
expect(submitButtons).toHaveLength(3);// expect 3 elements
