Files
awesome-claude-code-toolkit/commands/testing/snapshot-test.md
Rohit Ghumare c3f43d8b61 Expand toolkit to 135 agents, 120 plugins, 796 total files
- Add 60 new agents across all 10 categories (75 -> 135)
- Add 95 new plugins with command files (25 -> 120)
- Update all agents to use model: opus
- Update README with complete plugin/agent tables
- Update marketplace.json with all 120 plugins
2026-02-04 21:08:28 +00:00

1.5 KiB

Generate snapshot tests for UI components or serializable outputs.

Steps

  1. Identify the target component or function from the argument.
  2. Detect the testing framework and snapshot support (Jest snapshots, Vitest, pytest-snapshot).
  3. Analyze the component props or function parameters to determine meaningful test cases.
  4. For each component or function:
    • Create a snapshot test with default props/arguments.
    • Create snapshot tests for each significant visual state (loading, error, empty, populated).
    • Create snapshot tests for responsive variants if applicable.
  5. For React/Vue components, use the appropriate renderer:
    • @testing-library/react with render for DOM snapshots.
    • react-test-renderer for tree snapshots if needed.
  6. Run the tests to generate initial snapshots.
  7. List all generated snapshot files and their locations.

Format

Generated: <N> snapshot tests in <file>

Snapshots:
  - <ComponentName> default rendering
  - <ComponentName> loading state
  - <ComponentName> error state
  - <ComponentName> with data

Snapshot file: <path to .snap file>

Rules

  • Snapshot tests should capture meaningful visual states, not implementation details.
  • Avoid snapshotting entire page trees; focus on individual components.
  • Use inline snapshots (toMatchInlineSnapshot) for small outputs under 20 lines.
  • Add a comment explaining what each snapshot verifies.
  • Do not snapshot timestamps, random IDs, or other non-deterministic values; use serializers to strip them.