b2acc9b115
### New Content - Learning Paths section in README (Junior/Senior/Power User/PM tracks) - examples/ folder with 18 ready-to-use templates: - 4 agents (code-reviewer, test-writer, security-auditor, refactoring) - 2 skills (TDD workflow, security checklist) - 3 commands (commit, review-pr, generate-tests) - 4 hooks (bash + PowerShell for security, formatting) - 3 config templates (settings, MCP, gitignore) - 2 memory templates (project + personal CLAUDE.md) ### Governance - CHANGELOG.md: Version history (1.0.0 → 1.1.0 → Unreleased) - CONTRIBUTING.md: Contribution guidelines for community ### Documentation - llms.txt: Updated structure with new files/folders This update makes the guide more actionable with concrete templates and provides clear learning paths for different skill levels. Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
88 lines
1.7 KiB
Markdown
88 lines
1.7 KiB
Markdown
# Generate Tests
|
|
|
|
Generate comprehensive tests for specified code.
|
|
|
|
## Instructions
|
|
|
|
1. Read the target file(s)
|
|
2. Identify testable units (functions, classes, methods)
|
|
3. Generate tests following project conventions
|
|
4. Ensure high coverage of edge cases
|
|
|
|
## Test Generation Process
|
|
|
|
### 1. Analyze Target
|
|
- Identify public interfaces
|
|
- Understand dependencies
|
|
- Note edge cases and boundaries
|
|
|
|
### 2. Detect Test Framework
|
|
Check for:
|
|
- `jest.config.js` → Jest
|
|
- `vitest.config.ts` → Vitest
|
|
- `pytest.ini` → pytest
|
|
- `mocha` in package.json → Mocha
|
|
|
|
### 3. Generate Tests
|
|
Follow the detected framework conventions.
|
|
|
|
## Test Categories
|
|
|
|
### Happy Path
|
|
Normal expected behavior with valid input.
|
|
|
|
### Edge Cases
|
|
- Empty inputs
|
|
- Null/undefined values
|
|
- Boundary values (0, -1, MAX_INT)
|
|
- Single item vs multiple items
|
|
|
|
### Error Cases
|
|
- Invalid input types
|
|
- Missing required parameters
|
|
- Network/IO failures
|
|
- Timeout scenarios
|
|
|
|
### Integration Points
|
|
- Database interactions
|
|
- External API calls
|
|
- File system operations
|
|
|
|
## Output Format
|
|
|
|
```typescript
|
|
describe('[ComponentName]', () => {
|
|
describe('[methodName]', () => {
|
|
// Happy path
|
|
it('should [expected behavior] when [condition]', () => {
|
|
// Arrange
|
|
// Act
|
|
// Assert
|
|
});
|
|
|
|
// Edge cases
|
|
it('should handle empty input', () => {});
|
|
it('should handle null values', () => {});
|
|
|
|
// Error cases
|
|
it('should throw when [invalid condition]', () => {});
|
|
});
|
|
});
|
|
```
|
|
|
|
## Conventions
|
|
|
|
- One assertion per test (when practical)
|
|
- Descriptive test names
|
|
- AAA pattern (Arrange-Act-Assert)
|
|
- No test interdependence
|
|
- Mock external dependencies
|
|
|
|
## Usage
|
|
|
|
```
|
|
/generate-tests src/utils/calculator.ts
|
|
/generate-tests src/services/
|
|
```
|
|
|
|
$ARGUMENTS
|