Files
ECC/.kiro/steering/testing.md
T
Eric BellavanceandClaude Opus 5.5 1e895858d0 docs(kiro): use always inclusion for always-on steering files
Kiro only loads steering files automatically in every conversation when
they use `inclusion: always`; `auto` loads them only when the request
matches the description. Switch the always-on steering files to
`always` and update README, install.sh and docs accordingly.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-01 13:23:13 -04:00

36 lines
899 B
Markdown

---
inclusion: always
name: testing
description: Testing requirements including 80% coverage, TDD workflow, and test types.
---
# 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 (framework chosen per language)
## 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