Question 1

How to test async components with React Testing Library?

Accepted Answer

Use the `findBy` queries which return promises, or wrap assertions in `waitFor`. For example, in the README's complex example, `await screen.findByRole('alert')` is used to wait for elements after async operations like API calls.

Question 2

React Testing Library vs Enzyme: which is better for my project?

Accepted Answer

React Testing Library is better for behavior-driven tests that survive refactors and focus on user interactions, while Enzyme allows deeper access to component instances and internal state. RTL encourages more maintainable testing practices.

Question 3

How to mock API calls in React Testing Library tests?

Accepted Answer

The README recommends using Mock Service Worker (MSW) for declarative API mocking. The complex example shows setting up a server with `msw` to mock fetch requests, making tests more reliable and less brittle.

Question 4

Does React Testing Library work with TypeScript?

Accepted Answer

Yes, it has TypeScript support out of the box. The library provides type definitions, and many examples in the community are written in TypeScript, ensuring type safety in your tests.

Question 5

What are the best practices for writing tests with React Testing Library?

Accepted Answer

Focus on querying by accessible roles or text, avoid testing implementation details like state or props, and use `fireEvent` for user interactions. The README's guiding principles emphasize testing from the user's perspective.

Question 6

How to test custom hooks with React Testing Library?

Accepted Answer

For reusable hooks, use the separate React Hooks Testing Library. The README notes that single-use hooks should be tested via the components that use them, not in isolation, to align with user behavior.

react-testing-library

What is react-testing-library?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions