mirror of
https://github.com/affaan-m/everything-claude-code.git
synced 2026-02-02 04:33:08 +08:00
45959c326e
Battle-tested configs from 10+ months of daily Claude Code usage. Won Anthropic x Forum Ventures hackathon building zenith.chat. Includes: - 9 specialized agents (planner, architect, tdd-guide, code-reviewer, etc.) - 9 slash commands (tdd, plan, e2e, code-review, etc.) - 8 rule files (security, coding-style, testing, git-workflow, etc.) - 7 skills (coding-standards, backend-patterns, frontend-patterns, etc.) - Hooks configuration (PreToolUse, PostToolUse, Stop) - MCP server configurations (15 servers) - Plugin/marketplace documentation - Example configs (project CLAUDE.md, user CLAUDE.md, statusline) Read the full guide: https://x.com/affaanmustafa/status/2012378465664745795
31 lines
804 B
Markdown
31 lines
804 B
Markdown
# Testing Requirements
|
|
|
|
## Minimum Test Coverage: 80%
|
|
|
|
Test Types (ALL required):
|
|
1. **Unit Tests** - Individual functions, utilities, components
|
|
2. **Integration Tests** - API endpoints, database operations
|
|
3. **E2E Tests** - Critical user flows (Playwright)
|
|
|
|
## Test-Driven Development
|
|
|
|
MANDATORY workflow:
|
|
1. Write test first (RED)
|
|
2. Run test - it should FAIL
|
|
3. Write minimal implementation (GREEN)
|
|
4. Run test - it should PASS
|
|
5. Refactor (IMPROVE)
|
|
6. Verify coverage (80%+)
|
|
|
|
## Troubleshooting Test Failures
|
|
|
|
1. Use **tdd-guide** agent
|
|
2. Check test isolation
|
|
3. Verify mocks are correct
|
|
4. Fix implementation, not tests (unless tests are wrong)
|
|
|
|
## Agent Support
|
|
|
|
- **tdd-guide** - Use PROACTIVELY for new features, enforces write-tests-first
|
|
- **e2e-runner** - Playwright E2E testing specialist
|