test-driven-development
SolidUse when implementing any feature or bugfix, before writing implementation code. Enforces red-green-refactor cycle with strict rules.
AI & Automation 228 stars
13 forks Updated 3 weeks ago MIT
Install
Quality Score: 84/100
Stars 20%
Recency 20%
Frontmatter 20%
Documentation 15%
Issue Health 10%
License 10%
Description 5%
Skill Content
# Test-Driven Development (TDD)
## Rule
Write the test first. Watch it fail. Write minimal code to pass.
**Core principle:** If you didn't watch the test fail, you don't know if it tests the right thing.
## When to Use
Always for:
- New features
- Bug fixes
- Refactoring with behavior changes
Skip only for:
- Config file changes
- Documentation updates
- Non-functional changes (formatting, comments)
## Process
1. **Red**: Write a failing test
2. **Green**: Write minimal code to pass
3. **Refactor**: Clean up while keeping tests green
## Anti-Patterns
- Writing implementation before the test
- Skipping the "watch it fail" step
- Writing tests that are too coupled to implementation
- Testing framework behavior instead of your code
Details
- Author
- peintune
- Repository
- peintune/runjam
- Created
- 2 months ago
- Last Updated
- 3 weeks ago
- Language
- Rust
- License
- MIT
Similar Skills
Semantically similar based on skill content — not just same category
AI & Automation Listed
test-driven-development
Use when implementing any feature or bugfix, before writing implementation code.
0 Updated today
sipandey AI & Automation Listed
test-driven-development
Use when implementing any feature or bugfix, before writing implementation code
10 Updated today
dork-labs AI & Automation Listed
test-driven-development
Use when implementing any feature or bugfix, before writing implementation code
58 Updated today
The-AIOS