vitest-testing
Vitest testing framework for unit, component, and integration tests. Covers test structure (describe/it/test.each), assertions with expect, lifecycle hooks, mocking (vi.fn/vi.mock/vi.spyOn), React Testing Library patterns, hook testing with renderHook, user-event interactions, async utilities, configuration, workspace setup, coverage, and advanced patterns like in-source testing and concurrent execution. Also covers CLI commands, test filtering, tags, sharding, fixtures with test.extend, and fixture scoping. Use when writing unit tests, component tests, integration tests, or testing React hooks. Use for test configuration, mocking modules, testing async behavior, snapshot testing, or setting up test coverage.
What this skill does
# Vitest Testing
## Overview
Vitest is a Vite-native unit testing framework that shares the same configuration and plugin ecosystem. Built for speed with native ESM support, hot module replacement for tests, and parallel execution.
**When to use:** Unit tests, component tests, integration tests, hook tests, in-source tests. Testing React components with React Testing Library. Testing TanStack Query/Router/Form patterns.
**When NOT to use:** End-to-end testing (use Playwright), visual regression testing (use Percy/Chromatic), load testing (use k6).
## Quick Reference
| Pattern | API | Key Points |
| ------------------- | ----------------------------------------------- | ----------------------------------- |
| Test structure | `describe('suite', () => {})` | Organize related tests |
| Single test | `test('behavior', () => {})` or `it()` | Both are aliases |
| Parameterized tests | `test.each([...])('name', (arg) => {})` | Run same test with different inputs |
| Concurrent tests | `test.concurrent('name', async () => {})` | Run tests in parallel |
| Skip test | `test.skip('name', () => {})` or `skipIf(cond)` | Conditionally skip tests |
| Only test | `test.only('name', () => {})` | Run specific test for debugging |
| Assertions | `expect(value).toBe(expected)` | Compare primitive values |
| Deep equality | `expect(obj).toEqual(expected)` | Compare objects/arrays |
| Async assertions | `await expect(promise).resolves.toBe(value)` | Test promise resolution |
| Before each test | `beforeEach(() => {})` | Setup before each test |
| After each test | `afterEach(() => {})` | Cleanup after each test |
| Mock function | `vi.fn()` | Create spy function |
| Mock module | `vi.mock('./module')` | Replace entire module |
| Spy on method | `vi.spyOn(obj, 'method')` | Track calls to existing method |
| Clear mocks | `vi.clearAllMocks()` | Clear call history |
| Fake timers | `vi.useFakeTimers()` | Control setTimeout/setInterval |
| Render component | `render(<Component />)` | Mount React component for testing |
| Query by role | `screen.getByRole('button')` | Find elements by accessibility role |
| User interaction | `await user.click(element)` | Simulate user events |
| Wait for change | `await waitFor(() => expect(...))` | Wait for async changes |
| Find async element | `await screen.findByText('text')` | Query + wait combined |
| Render hook | `renderHook(() => useHook())` | Test custom hooks |
| Update hook props | `rerender(newProps)` | Re-render hook with new props |
| Snapshot | `expect(value).toMatchSnapshot()` | Compare against saved snapshot |
| Inline snapshot | `expect(value).toMatchInlineSnapshot()` | Snapshot stored in test file |
| CLI run once | `vitest run` | Single run, no watch |
| Run changed tests | `vitest --changed` | Tests affected by git changes |
| Filter by name | `vitest -t "pattern"` | Grep test names |
| Soft assertions | `expect.soft(value).toBe(x)` | Continue on failure, collect all |
| Poll assertions | `await expect.poll(() => val).toBe(x)` | Retry until passing |
| Test fixtures | `const test = base.extend<F>({...})` | Reusable setup via test.extend |
| Hoisted mocks | `vi.hoisted(() => ({ fn: vi.fn() }))` | Variables for vi.mock factory |
| Shard tests | `vitest --shard 1/3` | Split across CI workers |
| Tags | `test('name', { tags: ['slow'] }, ...)` | Filter with --tags-filter |
| Stub globals | `vi.stubGlobal('fetch', vi.fn())` | Replace global objects cleanly |
## Common Mistakes
| Mistake | Correct Pattern |
| -------------------------------------- | --------------------------------------------------- |
| Using `getBy` for async content | Use `findBy` or `waitFor` for async |
| Testing implementation details | Test behavior and public API |
| Using `getByTestId` as first choice | Prefer `getByRole`, `getByLabelText`, `getByText` |
| Missing `userEvent.setup()` | Always call `const user = userEvent.setup()` first |
| Shared state between tests | Use `beforeEach` to reset or create fresh instances |
| Not cleaning up mocks | Use `vi.clearAllMocks()` in `afterEach` |
| Mocking too much | Only mock external dependencies and APIs |
| Not disabling retries in tests | Set `retry: false` for TanStack Query tests |
| Immediate assertions on async | Use `await waitFor()` or `findBy` queries |
| Creating QueryClient in render | Create once in wrapper or use `useState` |
| Testing library code | Trust the library, test your usage |
| Not awaiting user events | All `user.*` methods return promises |
| Using `act` manually | `userEvent` and Testing Library handle this |
| Inline select without memoization | Extract to stable function for TanStack Query |
| Variables in vi.mock factory | Use `vi.hoisted()` to declare mock variables |
| Single `expect` for multiple checks | Use `expect.soft()` to collect all failures |
| `setTimeout` in tests for async waits | Use `expect.poll()` or `vi.waitFor()` |
| Manual `beforeEach` for reusable setup | Use `test.extend` fixtures for composable setup |
## Delegation
- **Test discovery**: For finding untested code paths, use `Explore` agent
- **Coverage analysis**: For full coverage review, use `Task` agent
- **E2E testing**: If `playwright` skill is available, delegate E2E testing to it
- **Code review**: After writing tests, delegate to `code-reviewer` agent
## References
- [Test fundamentals: structure, assertions, lifecycle hooks](references/test-fundamentals.md)
- [Mocking: vi.fn, vi.mock, vi.spyOn, module mocking](references/mocking.md)
- [Component testing: React Testing Library, queries, user-event](references/component-testing.md)
- [Hook testing: renderHook, async hooks, TanStack patterns](references/hook-testing.md)
- [Test setup: jest-dom matchers, cleanup, custom render, MSW, polyfills](references/test-setup.md)
- [Configuration: vitest.config.ts, workspace, coverage, reporters](references/configuration.md)
- [Advanced patterns: snapshots, concurrent tests, in-source, type testing](references/advanced-patterns.md)
- [CLI and filtering: commands, watch mode, tags, sharding](references/cli-and-filtering.md)
- [Fixtures and context: test.extend, scoping, auto fixtures, injection](references/fixtures-and-context.md)
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.