smithery.ai

component-testing

Enforces project React component testing conventions using Testing Library with proper rendering, user interactions, and accessibility testing.

First seen Mar 19, 2026

Installation

$ npx skills add https://smithery.ai

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from smithery.ai · top by installs.

npx skills add https://smithery.ai

Browse all from smithery.ai

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,863 B
  • docs SUMMARY.md 168 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 4 installs

SKILL.md

Component Testing Skill

Purpose

This skill provides React component testing conventions using Testing Library. Component tests verify rendering, user interactions, and accessibility of React components.

Activation

This skill activates when:

  • Creating or modifying files in tests/components/
  • Testing React components (.tsx files)
  • Working with Testing Library
  • Testing user interactions with userEvent

File Patterns

  • tests/components/**/*.test.tsx

Workflow

  1. Detect component test work (file path contains tests/components/)
  2. Load references/Component-Testing-Conventions.md
  3. Also load testing-base skill for shared conventions
  4. Apply component test patterns with Testing Library
  5. Ensure accessibility-first query usage

Key Patterns (REQUIRED)

Custom Render

  • ALWAYS use customRender from tests/setup/test-utils.tsx
  • Returns { user, ...renderResult } with pre-configured userEvent
  • Includes all providers (theme, clerk, etc.)

Testing Library Queries

  • Prefer getByRole for accessibility
  • Use getByTestId with namespace pattern (ui-, feature-, form-\*)
  • Use getByText, getByLabelText for content
  • Use queryBy* for assertions on missing elements

User Interactions

  • Use user from customRender return (pre-configured userEvent)
  • Always await user interactions
  • Test real user behaviors, not implementation details

Pre-Mocked Dependencies

  • Clerk, Next.js navigation, sonner, next-themes are pre-mocked
  • Mock server actions with vi.mock()

References

  • references/Component-Testing-Conventions.md - Complete component testing conventions