react-testing-library

React Testing Library guides you through writing tests that mirror real user behavior rather than internal implementation. It emphasizes querying by role, label, and text—prioritizing accessibility—and provides utilities for simulating user interactions, handling async operations, and debugging. Master query types, user events, and common patterns like custom renders and hook testing.

React Testing Library helps you write React component unit tests using accessible queries and user-event simulation.

AI-generated summary based on this skill's SKILL.md

★ 21 ⁮ 1 MIT updated 2026-07-18 by itechmeat

Install

itechmeat/llm-code/react-testing-library · repository language: Go

Manual (git clone) CLI (skillfed)

git clone https://github.com/itechmeat/llm-code
cp -r llm-code/skills/react-testing-library ~/.claude/skills/react-testing-library

npx skillfed install itechmeat/llm-code/react-testing-library

Frequently asked questions

AI-generated answers based on this skill's SKILL.md and metadata

How do I test React components with testing library?

React Testing Library provides utilities to write tests that simulate real user behavior. Start by rendering your component with `render()`, then query elements using accessible queries like `getByRole()`, `getByLabelText()`, or `getByText()`. Simulate user interactions with `userEvent`, and use `findBy` or `waitFor()` for async operations. This approach prioritizes accessibility and makes tests more maintainable.

What are the main query types in React Testing Library?

React Testing Library offers three query variants: `getBy*` (throws if not found), `queryBy*` (returns null if absent), and `findBy*` (returns a promise for async elements). Query types include `getByRole()` for accessible elements, `getByLabelText()` for form inputs, `getByText()` for content, and `getByPlaceholderText()` for inputs. Role-based queries are preferred as they reflect how users interact with your app.

How should I simulate user interactions instead of fireEvent?

React Testing Library recommends using `userEvent` instead of `fireEvent` because it simulates real user behavior more accurately. Import `userEvent` from '@testing-library/user-event', then use methods like `userEvent.click()`, `userEvent.type()`, `userEvent.selectOptions()`, and `userEvent.hover()`. UserEvent fires multiple events in sequence, matching how browsers handle actual user input, making tests more reliable.

What patterns should I use for testing async behavior?

React Testing Library provides `findBy*` queries and `waitFor()` for async testing. Use `findBy*` when expecting elements to appear after async operations—it returns a promise that resolves when found. For more complex async scenarios, wrap assertions in `waitFor()` to poll until conditions are met. Avoid `act()` warnings by letting Testing Library handle updates automatically through user interactions and async queries.

How do I test React hooks with renderHook?

React Testing Library's `renderHook()` utility lets you test hooks in isolation. Import it from '@testing-library/react', call `renderHook(() => useMyHook())`, and access the hook's return value via `result.current`. For async hooks, use `waitFor()` to wait for state updates. Pass props through the `initialProps` option and update them with `rerender()` to test how hooks respond to prop changes.

What accessibility-first testing patterns does React Testing Library promote?

React Testing Library prioritizes accessible queries to encourage writing inclusive components. Use `getByRole()` to query semantic elements, `getByLabelText()` for form fields, and avoid implementation details like test IDs when possible. This approach ensures your tests verify that components work for all users, including those using assistive technologies. Custom render functions with providers and jest-dom matchers enhance accessibility testing.

SKILL.md

rendered from the published skill — quoted content, verbatim