Skip to content
Back to skills

React Testing

ASecurity

Use when writing or fixing tests for React components, hooks, or pages with Testing Library, Vitest/Jest, MSW, and axe. Triggers on \"react-testing\", \"react testing\", \"testing\".

  • 2 stars
  • 0 votes
  • 0 copies
  • 2 views
  • Added September 19, 2026
ai-agentsreacttestingapi

Works with

  • cli
  • api

Security analysis

A100/100

Pro scans all 5 files and shows the line behind each finding

Scanned September 19, 2026

npx -y skills add majinmagros/magros.ai-skills --skill react-testing --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of React Testing?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for React Testing
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/majinmagros-react-testing/badge)](https://www.skillsdirectory.com/skills/majinmagros-react-testing)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: react-testing
description: "Use when writing or fixing tests for React components, hooks, or pages with Testing Library, Vitest/Jest, MSW, and axe. Triggers on \"react-testing\", \"react testing\", \"testing\"."
metadata:
  origin: ECC
---

# React Testing

Behavior-focused React component, hook, and page tests. Detalhes em `references/`.

## When to Activate

- Writing tests for React components, custom hooks, or pages
- Adding test coverage to legacy untested components
- Migrating from Enzyme or class-component-era patterns to React Testing Library
- Setting up Vitest or Jest for a new React project
- Mocking HTTP requests in tests
- Asserting accessibility violations

## Core Principles

1. **Test behavior, not internals** — visible output and side effects, never state/props/render counts
2. **Accessible queries first** — `getByRole` > semantic > `getByTestId` (last resort)
3. **`userEvent` over `fireEvent`** — `setup()` once per test, always `await`
4. **Async via `findBy`/`waitFor`** — never `setTimeout` + assertion
5. **MSW at the network layer** — `onUnhandledRequest: "error"`, per-test `server.use` overrides

## Example

```tsx
test("submits the form", async () => {
  const user = userEvent.setup();
  const onSubmit = vi.fn();
  render(<UserForm onSubmit={onSubmit} />);

  await user.type(screen.getByLabelText("Email"), "user@example.com");
  await user.click(screen.getByRole("button", { name: /save/i }));

  expect(onSubmit).toHaveBeenCalledWith({ email: "user@example.com" });
});
```

## References

- `references/queries-interaction.md` — runner choice, query priority, `userEvent`, async patterns
- `references/network-providers.md` — MSW setup/override, provider wrapping, hook testing
- `references/a11y-snapshots-e2e.md` — axe, snapshot limits, Playwright/Cypress boundary, coverage, anti-patterns
- `references/tdd-commands-examples.md` — TDD workflow, test commands, related, full examples

## Checklist

- [ ] Queries by role/label, `getByTestId` only as escape hatch
- [ ] Providers wrapped once in `test-utils`; QueryClient `retry: false`
- [ ] MSW `onUnhandledRequest: "error"`; no unmocked network passes silently
- [ ] axe green on interactive components; no DOM snapshots
- [ ] RTL for logic, Playwright CT for browser APIs, E2E for multi-page flows

Files in this skill

  • SKILL.md2.3 KB
  • references/a11y-snapshots-e2e.md3.2 KB
  • references/network-providers.md3.3 KB
  • references/queries-interaction.md2.8 KB
  • references/tdd-commands-examples.md2.8 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…