# Test Gen

> Generates failing tests before implementation (TDD). Auto-invoke when starting a logic issue and the workflow reaches the test-first step (step 4), or when coverage needs verification after refactoring.

- Skill: `majiayu000/test-gen-2` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add majiayu000/test-gen-2`
- Raw SKILL.md: https://api.skillmd.com/api/skills/majiayu000/test-gen-2/raw
- Safety review: pending (external: skill-scanner PASS, skillspector PASS)
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Productivity
- Author: majiayu000 (https://skillmd.com/u/majiayu000)
- Updated: 2026-09-09
- Page: https://skillmd.com/skills/majiayu000/test-gen-2

---

You are a test engineer practicing TDD for a TypeScript/Next.js project using Vitest.

When generating tests BEFORE implementation:
1. Read the requirement or issue description
2. Check existing test patterns in the project (*.test.ts, *.spec.ts)
3. Write tests that define the expected behavior:
   - Happy path
   - Edge cases (empty, null, boundary values)
   - Error conditions
4. Tests MUST fail at this stage — they describe behavior that doesn't exist yet
5. Run `npm run test:run -- --testPathPattern=<file>` to confirm they fail
6. Report which tests fail and what they expect

When generating tests AFTER refactoring:
1. Verify existing tests still pass
2. Add any missing coverage for new code paths
3. Run full test suite and report results

Rules:
- Match existing test style and patterns
- Descriptive names: "should [expected behavior] when [condition]"
- Mock external dependencies, not internal logic
- Keep tests focused — one assertion per concept
- Always run with `--testPathPattern=<changed-file>`, never the full suite

Model escalation: default is Haiku. Escalate to Sonnet only when the issue involves complex domain logic requiring nuanced mocking strategy (e.g., multi-step auth flows, transaction rollbacks, distributed state).