react-testing
React Testing Library patterns for component testing
What this skill does
# React Testing Skill
Patterns for testing React components with React Testing Library.
## Testing Philosophy
React Testing Library encourages testing components the way users interact with them, not implementation details.
### The Guiding Principles
1. Test behavior, not implementation
2. Find elements like a user would
3. Interact like a user would
4. Assert on what the user sees
## Rendering Components
### Basic Rendering
```tsx
import { render, screen } from '@testing-library/react'
test('renders greeting', () => {
render(<Greeting name="World" />)
expect(screen.getByText('Hello, World!')).toBeInTheDocument()
})
```
### Rendering with Providers
```tsx
function renderWithProviders(
ui: ReactElement,
{
preloadedState = {},
...renderOptions
} = {}
) {
function Wrapper({ children }: { children: ReactNode }) {
return (
<Provider store={setupStore(preloadedState)}>
<ThemeProvider>
<Router>
{children}
</Router>
</ThemeProvider>
</Provider>
)
}
return render(ui, { wrapper: Wrapper, ...renderOptions })
}
// Usage
test('renders with providers', () => {
renderWithProviders(<UserDashboard />)
expect(screen.getByText('Dashboard')).toBeInTheDocument()
})
```
## Queries
### Query Priority
Use queries in this order (most to least preferred):
```tsx
// 1. Accessible queries (preferred)
screen.getByRole('button', { name: /submit/i })
screen.getByLabelText('Email')
screen.getByPlaceholderText('Enter email')
screen.getByText('Hello World')
screen.getByDisplayValue('current value')
// 2. Semantic queries
screen.getByAltText('Profile picture')
screen.getByTitle('Close')
// 3. Test IDs (last resort)
screen.getByTestId('custom-element')
```
### Query Variants
```tsx
// getBy* - Throws if not found (use for elements that should exist)
screen.getByRole('button')
// queryBy* - Returns null if not found (use for asserting absence)
expect(screen.queryByText('Loading')).not.toBeInTheDocument()
// findBy* - Returns promise, waits for element (use for async)
const button = await screen.findByRole('button')
// *AllBy* - Returns array of all matches
const items = screen.getAllByRole('listitem')
```
### Role-Based Queries
```tsx
// Buttons
screen.getByRole('button', { name: /submit/i })
// Links
screen.getByRole('link', { name: /home/i })
// Form elements
screen.getByRole('textbox', { name: /email/i })
screen.getByRole('checkbox', { name: /remember me/i })
screen.getByRole('combobox', { name: /country/i })
// Headings
screen.getByRole('heading', { name: /welcome/i, level: 1 })
// Navigation
screen.getByRole('navigation')
// Lists
screen.getByRole('list')
screen.getAllByRole('listitem')
```
## User Interactions
### Click Events
```tsx
import { render, screen } from '@testing-library/react'
import userEvent from '@testing-library/user-event'
test('button click increments counter', async () => {
const user = userEvent.setup()
render(<Counter />)
const button = screen.getByRole('button', { name: /increment/i })
await user.click(button)
expect(screen.getByText('Count: 1')).toBeInTheDocument()
})
```
### Typing
```tsx
test('form submission', async () => {
const user = userEvent.setup()
const onSubmit = jest.fn()
render(<LoginForm onSubmit={onSubmit} />)
await user.type(screen.getByLabelText(/email/i), '[email protected]')
await user.type(screen.getByLabelText(/password/i), 'password123')
await user.click(screen.getByRole('button', { name: /sign in/i }))
expect(onSubmit).toHaveBeenCalledWith({
email: '[email protected]',
password: 'password123',
})
})
```
### Select and Keyboard
```tsx
test('select option', async () => {
const user = userEvent.setup()
render(<CountrySelect />)
await user.selectOptions(
screen.getByRole('combobox', { name: /country/i }),
'US'
)
expect(screen.getByRole('combobox')).toHaveValue('US')
})
test('keyboard navigation', async () => {
const user = userEvent.setup()
render(<Form />)
await user.tab() // Focus first input
await user.type(screen.getByLabelText(/name/i), 'John')
await user.tab() // Focus next input
await user.keyboard('{Enter}') // Submit form
})
```
## Async Testing
### Waiting for Elements
```tsx
test('loads user data', async () => {
render(<UserProfile userId="123" />)
// Wait for loading to finish
expect(screen.getByText(/loading/i)).toBeInTheDocument()
// Wait for data to appear
expect(await screen.findByText('John Doe')).toBeInTheDocument()
})
```
### waitFor
```tsx
import { waitFor } from '@testing-library/react'
test('form validation', async () => {
const user = userEvent.setup()
render(<Form />)
await user.click(screen.getByRole('button', { name: /submit/i }))
await waitFor(() => {
expect(screen.getByText(/email is required/i)).toBeInTheDocument()
})
})
test('disappearing element', async () => {
render(<Notification />)
expect(screen.getByText(/success/i)).toBeInTheDocument()
await waitFor(() => {
expect(screen.queryByText(/success/i)).not.toBeInTheDocument()
})
})
```
### waitForElementToBeRemoved
```tsx
test('loading state disappears', async () => {
render(<DataLoader />)
await waitForElementToBeRemoved(() => screen.queryByText(/loading/i))
expect(screen.getByText('Data loaded')).toBeInTheDocument()
})
```
## Mocking
### Mocking API Calls
```tsx
import { rest } from 'msw'
import { setupServer } from 'msw/node'
const server = setupServer(
rest.get('/api/user/:id', (req, res, ctx) => {
return res(ctx.json({ id: req.params.id, name: 'John Doe' }))
})
)
beforeAll(() => server.listen())
afterEach(() => server.resetHandlers())
afterAll(() => server.close())
test('fetches user data', async () => {
render(<UserProfile userId="123" />)
expect(await screen.findByText('John Doe')).toBeInTheDocument()
})
test('handles error', async () => {
server.use(
rest.get('/api/user/:id', (req, res, ctx) => {
return res(ctx.status(500))
})
)
render(<UserProfile userId="123" />)
expect(await screen.findByText(/error loading user/i)).toBeInTheDocument()
})
```
### Mocking Hooks
```tsx
jest.mock('../hooks/useUser', () => ({
useUser: jest.fn(),
}))
import { useUser } from '../hooks/useUser'
test('renders user when loaded', () => {
(useUser as jest.Mock).mockReturnValue({
user: { name: 'John' },
loading: false,
error: null,
})
render(<UserProfile />)
expect(screen.getByText('John')).toBeInTheDocument()
})
```
### Mocking Router
```tsx
import { MemoryRouter, Route, Routes } from 'react-router-dom'
test('navigates on click', async () => {
const user = userEvent.setup()
render(
<MemoryRouter initialEntries={['/']}>
<Routes>
<Route path="/" element={<Home />} />
<Route path="/about" element={<About />} />
</Routes>
</MemoryRouter>
)
await user.click(screen.getByRole('link', { name: /about/i }))
expect(screen.getByText(/about page/i)).toBeInTheDocument()
})
```
## Component Testing Patterns
### Testing Forms
```tsx
describe('RegistrationForm', () => {
test('shows validation errors for empty required fields', async () => {
const user = userEvent.setup()
render(<RegistrationForm />)
await user.click(screen.getByRole('button', { name: /register/i }))
expect(await screen.findByText(/name is required/i)).toBeInTheDocument()
expect(screen.getByText(/email is required/i)).toBeInTheDocument()
})
test('submits with valid data', async () => {
const user = userEvent.setup()
const onSubmit = jest.fn()
render(<RegistrationForm onSubmit={onSubmit} />)
await user.type(screen.getByLabelText(/name/i), 'John Doe')
await user.type(screen.getByLabelText(/email/i), '[email protected]')
await user.click(screen.getByRole('button', { name: /register/i }))
expect(onSubmit).toHaveBeenCalledWith({
name: 'John Doe',
email: '[email protected]',
Related in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.