React Testing Library
lastmod 2025-03-18created 2023-07-055 edits
Simple and complete React DOM testing utilities that encourage good testing practices.
Installation
Example
import {render, screen} from '@testing-library/react';
import Button from './Button';
describe('Button', () => {
const props = {
caption: 'test-button-title',
};
it('Render', () => {
render(<Button {...props} />);
const root = screen.getByTestId('root');
const caption = screen.getByTestId('caption');
expect(root).toBeDefined();
expect(caption).toBeDefined();
});
});
Troubleshooting
Jest encountered an unexpected token
Ran into the following error:
$ ./yarn test
FAIL src/lib/Button.spec.tsx
● Test suite failed to run
Jest encountered an unexpected token
Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax.
Out of the box Jest supports Babel, which will be used to transform your files into valid JS based on your Babel configuration.
By default "node_modules" folder is ignored by transformers.
Here's what you can do:
• If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/ecmascript-modules for how to enable it.
• If you are trying to use TypeScript, see https://jestjs.io/docs/getting-started#using-typescript
• To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config.
• If you need a custom transformation specify a "transform" option in your config.
• If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option.
You'll find more details and examples of these config options in the docs:
https://jestjs.io/docs/configuration
For information about custom transformations, see:
https://jestjs.io/docs/code-transformation
Details:
/home/your/Project/your-ui/src/lib/Button.module.scss:1
({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,jest){.root {
^
SyntaxError: Unexpected token '.'
1 | import * as React from 'react';
> 2 | import styles from './Button.module.scss';
| ^
3 |
4 | export interface ButtonProps {
5 | caption?: string;
at Runtime.createScriptFromCode (node_modules/jest-runtime/build/index.js:1495:14)
at Object.<anonymous> (src/lib/Button.tsx:2:1)
at Object.<anonymous> (src/lib/Button.spec.tsx:2:1)
Test Suites: 1 failed, 1 total
Tests: 0 total
Snapshots: 0 total
Time: 1.763 s
Ran all test suites.
It appears to be failing to interpret the Button.module.scss file.
Install the following packages:
Change moduleNameMapper in the jest configuration as follows:
"jest": {
"preset": "ts-jest",
"testEnvironment": "jsdom",
"moduleNameMapper": {
"\\.(css|sass|scss)$": "identity-obj-proxy",
"\\.svg": "jest-svg-transformer"
}
},
See also
Favorite site
- React Testing Library | Testing Library
- Testing Overview – React
- testing-library/react-testing-library
- Test Environment in React by using Vite - Junhyunny’s Devlogs
- Writing React test code with Jest + react testing library - Coding as I feel
- How The New York Times switched from Enzyme to React Testing Library | GeekNews
- [Original] How The New York Times systematically migrated from Enzyme into React Testing Library | by Felipe Buenano | The NYT Open Team | NYT Open
- While upgrading from React 16 to React 18, NYT switched its testing utility from Enzyme to React Testing Library
- It had used Enzyme since 2016, but the switch became necessary as the React platform recommended React Testing Library
Pages that link here