Test Driven Development
Testing & Qualitytest-driven-developmentTest Driven Development is an Agent Skill for testing & quality published in the a5c-ai/babysitter repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.
Test-first development practice where test specifications are written before production code, integrated into plan tasks as mandatory first sub-steps.
QUICK START
How to use this skill
Bring this guide into your coding agent with a prompt tailored to the tool you use.
- Open your project in Codex.
- Copy and paste the prompt below.
- Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/a5c-ai/babysitter/blob/HEAD/library/methodologies/rpikit/skills/test-driven-development/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/test-driven-development, but wait for my approval before writing files or running scripts.
Copying this prompt does not install or run the skill. Review third-party files before use.
- During implementation (write tests before code)
- When verifying step completion
Process
- Specify tests first - Define inputs, expected outputs, edge cases
- Write test code - Create automated tests matching specification
- Implement production code - Write code that passes the tests
- Verify - Run tests and confirm all pass
Test Categories
- Unit tests: Isolated function/method testing
- Integration tests: Cross-component interaction testing
- Manual verification: Human-performed checks when automation is impractical
Key Rules
- Never combine test writing and implementation into a single step
- Every task with code changes must have associated tests
- Tests must be runnable and produce clear pass/fail results
- Edge cases must be explicitly considered
Tool Use
Integrated into methodologies/rpikit/rpikit-plan and methodologies/rpikit/rpikit-implement