Security News
New Python Packaging Proposal Aims to Solve Phantom Dependency Problem with SBOMs
PEP 770 proposes adding SBOM support to Python packages to improve transparency and catch hidden non-Python dependencies that security tools often miss.
@metaphor-xyz/react-native-testing-library
Advanced tools
Simple and complete React Native testing utilities that encourage good testing practices, modified to work with React Native Web.
Simple and complete React Native testing utilities that encourage good testing practices.
NOTE: This is a Metaphor maintained soft fork to attempt to make this library more compatible with React Native Web.
We renamed the
react-native-testing-library
npm package to@testing-library/react-native
, officially joining the "Testing Library" family 🎉. Read the migration guide.
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.
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. Tested to work with Jest, but it should work with other test runners as well.
Open a Terminal in your project's folder and run:
yarn
yarn add --dev @testing-library/react-native
npm
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 andwaitFor
) you need at least React >=16.9.0 (featuring asyncact
) or React Native >=0.61 (which comes with React >=16.9.0).
In order to use additional React Native-specific jest matchers from @testing-library/jest-native package add it to your project:
yarn
yarn add --dev @testing-library/jest-native
npm
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):
{
"preset": "react-native",
"setupFilesAfterEnv": ["@testing-library/jest-native/extend-expect"]
}
important if you use "modern" Fake Timers
We generally advise to use the "react-native" preset when testing with this library. However, if you use "modern" Fake Timers (default since Jest 27), you'll need to apply our custom Jest preset or awaiting promises, like waitFor
, will timeout.
This is a known issue. 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:
{
"preset": "@testing-library/react-native"
}
If this doesn't work for you, please fall back to using "legacy" fake timers.
Note for Flow users – you'll also need to install typings for react-test-renderer
:
flow-typed install react-test-renderer
import { render, fireEvent } from '@testing-library/react-native';
import { QuestionsBoard } from '../QuestionsBoard';
test('form submits two answers', () => {
const allQuestions = ['q1', 'q2'];
const mockFn = jest.fn();
const { getAllByLabelText, getByText } = render(
<QuestionsBoard questions={allQuestions} onSubmit={mockFn} />
);
const answerInputs = getAllByLabelText('answer input');
fireEvent.changeText(answerInputs[0], 'a1');
fireEvent.changeText(answerInputs[1], 'a2');
fireEvent.press(getByText('Submit'));
expect(mockFn).toBeCalledWith({
'1': { q: 'q1', a: 'a1' },
'2': { q: 'q2', a: 'a2' },
});
});
You can find the source of QuestionsBoard
component and this example here.
The public API of @testing-library/react-native
is focused around these essential methods:
render
– deeply renders given React element and returns helpers to query the output components.fireEvent
- invokes named event handler on the element.waitFor
- waits for non-deterministic periods of time until queried element is added or times out.waitForElementToBeRemoved
- waits for non-deterministic periods of time until queried element is removed or times out.within
- creates a queries object scoped for given element.React Native Testing Library is an open source project and will always remain free to use. If you think it's cool, please star it 🌟. Callstack is a group of React and React Native geeks, contact us at hello@callstack.com if you need any help with these or just want to say hi!
Like the project? ⚛️ Join the team who does amazing stuff for clients and drives React Native Open Source! 🔥
Supported and used by Rally Health.
FAQs
Simple and complete React Native testing utilities that encourage good testing practices, modified to work with React Native Web.
We found that @metaphor-xyz/react-native-testing-library demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
PEP 770 proposes adding SBOM support to Python packages to improve transparency and catch hidden non-Python dependencies that security tools often miss.
Security News
Socket CEO Feross Aboukhadijeh discusses open source security challenges, including zero-day attacks and supply chain risks, on the Cyber Security Council podcast.
Security News
Research
Socket researchers uncover how threat actors weaponize Out-of-Band Application Security Testing (OAST) techniques across the npm, PyPI, and RubyGems ecosystems to exfiltrate sensitive data.