testgen
Generate tests using AI and run test suites. Use for generating unit tests, running coverage reports, and mutation testing.
What this skill does
# Test Generator
AI-powered test generation and test suite management.
## Prerequisites
```bash
# Gemini for AI generation
pip install google-generativeai
export GEMINI_API_KEY=your_api_key
# Test runners (install as needed)
npm install -D jest vitest mocha
npm install -D @stryker-mutator/core # Mutation testing
```
## AI Test Generation
### Generate Unit Tests
```bash
# Read code and generate tests
CODE=$(cat src/utils.ts)
gemini -m pro -o text -e "" "Generate comprehensive unit tests for this code:
$CODE
Requirements:
1. Use Jest/Vitest syntax
2. Cover happy path, edge cases, and error conditions
3. Include descriptive test names
4. Mock external dependencies
5. Test each exported function
Output only the test code, ready to save to a file."
```
### Generate Tests for Specific Function
```bash
gemini -m pro -o text -e "" "Generate unit tests for this function:
\`\`\`typescript
export function calculateDiscount(price: number, percentage: number): number {
if (percentage < 0 || percentage > 100) {
throw new Error('Invalid percentage');
}
return price * (1 - percentage / 100);
}
\`\`\`
Include tests for:
- Valid inputs
- Boundary values (0%, 100%)
- Invalid inputs (negative, >100)
- Edge cases (zero price)
Use Jest syntax."
```
### TDD Loop
```bash
# 1. Write failing test first
gemini -m pro -o text -e "" "Write a failing test for: [feature description]"
# 2. Run test (should fail)
npm test -- --watch
# 3. Implement minimal code to pass
# 4. Refactor
# 5. Repeat
```
## Test Runners
### Jest
```bash
# Run all tests
npx jest
# Watch mode
npx jest --watch
# Specific file
npx jest src/utils.test.ts
# With coverage
npx jest --coverage
# Update snapshots
npx jest -u
# Verbose output
npx jest --verbose
# Run matching pattern
npx jest -t "should calculate"
```
### Vitest
```bash
# Run tests
npx vitest
# Watch mode
npx vitest --watch
# Run once
npx vitest run
# Coverage
npx vitest --coverage
# UI mode
npx vitest --ui
# Specific file
npx vitest src/utils.test.ts
```
### Mocha
```bash
# Run tests
npx mocha
# Watch mode
npx mocha --watch
# Specific file
npx mocha test/utils.test.js
# With reporter
npx mocha --reporter spec
```
## Coverage Analysis
### Generate Coverage Report
```bash
# Jest
npx jest --coverage --coverageReporters=text --coverageReporters=html
# Vitest
npx vitest run --coverage
# View HTML report
open coverage/index.html
```
### Coverage Thresholds
```json
// jest.config.js or vitest.config.ts
{
"coverageThreshold": {
"global": {
"branches": 80,
"functions": 80,
"lines": 80,
"statements": 80
}
}
}
```
### Find Uncovered Code
```bash
# Text coverage report
npx jest --coverage --coverageReporters=text
# Ask AI for suggestions
UNCOVERED=$(npx jest --coverage --coverageReporters=json --silent | jq '.coverageMap')
gemini -m pro -o text -e "" "Given this coverage report, suggest tests for uncovered code:
$UNCOVERED"
```
## Mutation Testing
Test the tests themselves using Stryker:
```bash
# Check if installed
npx stryker --version
# Initialize
npx stryker init
# Run mutation testing
npx stryker run
# With reporters
npx stryker run --reporters clear-text,json,html
```
### Interpret Results
- **Killed mutants**: Tests caught the bug (good)
- **Survived mutants**: Tests missed the bug (need more tests)
- **Timeout mutants**: Mutant caused infinite loop
- **No coverage**: Code not covered by any test
## Workflow Patterns
### New Feature Testing
```bash
# 1. Generate test scaffold
CODE=$(cat src/new-feature.ts)
gemini -m pro -o text -e "" "Generate test file scaffold for: $CODE" > src/new-feature.test.ts
# 2. Run tests (should fail)
npx jest src/new-feature.test.ts
# 3. Implement feature
# 4. Run tests (should pass)
# 5. Add edge case tests
# 6. Check coverage
npx jest src/new-feature.test.ts --coverage
```
### Regression Test Generation
```bash
# After fixing a bug, generate regression test
BUG_DESC="Users could submit empty forms"
FIX=$(git diff HEAD~1)
gemini -m pro -o text -e "" "Generate a regression test for this bug fix:
Bug: $BUG_DESC
Fix:
$FIX
The test should fail if the bug is reintroduced."
```
### Integration Test Generation
```bash
gemini -m pro -o text -e "" "Generate integration tests for this API endpoint:
\`\`\`typescript
// POST /api/users
// Body: { name: string, email: string }
// Response: { id: string, name: string, email: string }
\`\`\`
Include:
- Success case
- Validation errors
- Duplicate email handling
- Authentication required
Use supertest or similar."
```
## Best Practices
1. **Test behavior, not implementation** - Focus on what, not how
2. **One assertion per test** - When practical
3. **Descriptive names** - Should document what's tested
4. **Arrange-Act-Assert** - Clear test structure
5. **Mock external deps** - Isolate unit under test
6. **Run tests in CI** - Automated verification
7. **Maintain coverage** - Don't let it drop
8. **Use mutation testing** - Verify test quality
Related in Code Review
gstack
IncludedFast headless browser for QA testing and site dogfooding. Navigate pages, interact with elements, verify state, diff before/after, take annotated screenshots, test responsive layouts, forms, uploads, dialogs, and capture bug evidence. Use when asked to open or test a site, verify a deployment, dogfood a user flow, or file a bug with screenshots. (gstack)
startup-due-diligence
IncludedLegal due diligence review for seed-stage and Series A startups (US, Delaware C-Corp focus). Supports both investor and founder perspectives. Capabilities include: (1) Interactive document review and issue spotting; (2) Document request list generation; (3) Cap table and SAFE/convertible note analysis; (4) Red flag identification with severity ratings; (5) Diligence report generation. TRIGGERS: due diligence, DD, startup investment, cap table review, Series A, seed round, investor diligence, legal review startup, SAFE analysis, convertible note, 409A, founder vesting.
interview-master
IncludedThis skill should be used when the user asks to "generate interview questions", "prepare for interview", "optimize resume", "conduct mock interview", "analyze git commits for resume", "generate resume from code", "review my resume", or mentions interview preparation, career assistance, or extracting project experience from git history. Provides comprehensive interview and career development guidance for both job seekers and interviewers.
fix-issue
IncludedFixes GitHub issues using parallel analysis agents for root cause investigation, code exploration, and regression detection. Reads issue context from gh CLI, searches codebase and memory for related patterns, generates a fix with tests, and links the resolution back to the issue via PR. Includes prevention analysis to avoid recurrence. Use when debugging errors, resolving regressions, fixing bugs, or triaging issues.
sf-apex
IncludedGenerates and reviews Salesforce Apex code with 150-point scoring. TRIGGER when: user writes, reviews, or fixes Apex classes, triggers, test classes, batch/queueable/schedulable jobs, or touches .cls/.trigger files. DO NOT TRIGGER when: LWC JavaScript (use sf-lwc), Flow XML (use sf-flow), SOQL-only queries (use sf-soql), or non-Salesforce code.
swift-development
IncludedComprehensive Swift development for building, testing, and deploying iOS/macOS applications. Use when Claude needs to: (1) Build Swift packages or Xcode projects from command line, (2) Run tests with XCTest or Swift Testing framework, (3) Manage iOS simulators with simctl, (4) Handle code signing, provisioning profiles, and app distribution, (5) Format or lint Swift code with SwiftFormat/SwiftLint, (6) Work with Swift Package Manager (SPM), (7) Implement Swift 6 concurrency patterns (async/await, actors, Sendable), (8) Create SwiftUI views with MVVM architecture, (9) Set up Core Data or SwiftData persistence, or any other Swift/iOS/macOS development tasks.