Test Generator
Generate comprehensive tests with advanced testing strategies, scenario generation, and edge case identification.
When to Activate
- User asks to write tests
- User mentions test coverage
- User wants unit, integration, or e2e tests
- After implementing new features (suggest tests)
- User asks about testing a specific file or function
Quick Process
- Analyze Code: Understand structure and dependencies
- Select Strategy: Choose testing approach based on code type
- Generate Tests: Create tests with appropriate framework
- Identify Edge Cases: Boundary conditions and error handling
- Return Files: Return the test file contents as artifacts. This skill has no Write tool and no Bash, so it cannot write to disk or measure coverage — do not claim a coverage figure, and name the behaviors you did not write a test for.
Options
| Option | Values | Default |
|---|---|---|
--framework |
jest, vitest, pytest, cypress, playwright | auto-detect |
--type |
unit, integration, e2e, all | unit |
--strategy |
standard, scenario, property, mutation | standard |
--requirements |
User stories for scenario generation | (none) |
Strategies
- Standard: Traditional unit testing with assertions
- Scenario: Behavior-driven from user stories (Given-When-Then)
- Property: Property-based testing for pure functions
- Mutation: Mutation testing to verify test quality
Edge Case Emphasis
Always identifies:
- Boundary values and null/undefined handling
- Overflow/underflow conditions
- Security edge cases (injection, XSS)
- Concurrency and race conditions
Delegation
Invoke test-writer-agent agent with:
paths: Files to testframework: Testing frameworktestType: Testing strategyrequirements: User stories (if provided)
For a single file or a few files in one module, invoke test-writer-agent directly — that is
the common case. Only for work spanning several areas, coordinate with
development-codebase-tools:context-loader-agent and
development-codebase-tools:security-analyzer-agent (both live in another plugin, hence the
prefix).
Examples
"Write tests for src/utils/validator.ts"
"Add integration tests for the API endpoints"
"Generate e2e tests for checkout flow"
"I need property-based tests for this pure function"
Detailed Reference
For advanced strategies and orchestration, see gen-tests-guide.md.