What problem does it solve? React tests often break on refactors because they assert on implementation details instead of user-visible behavior, and teams struggle to decide what belongs in component tests versus end-to-end runs. This Skill provides concrete patterns for writing stable, accessible, behavior-driven tests for React components and hooks. ## Core Features & Use Cases - Behavior-Focused Testing Patterns: Query priority guidance (getByRole first), userEvent interactions, and async patterns with findBy/waitFor to eliminate flaky tests. - Network Mocking with MSW: Mock Service Worker setup with per-test handler overrides so components and fetch logic behave exactly as in production. - Accessibility & Coverage: axe-based a11y assertions in component tests plus coverage thresholds for utilities, hooks, and components. - Use Case: When adding tests to a legacy React form component, use this Skill to render it with production providers, mock its API calls with MSW, simulate real user input with userEvent, and assert on visible success or error states. ## Quick Start Write a React Testing Library test for my UserForm component that mocks the POST /api/users endpoint with MSW and asserts the success message appears after submission.