Guide red-green-refactor cycles with behavior-focused integration tests.
npx skills add https://github.com/sumpalabs/petrodb --skill tdd-sumpalabs
Please help me install this Agent Skill. Skill: tdd Source: https://github.com/sumpalabs/petrodb/tree/main/.agents/skills/tdd Command: npx skills add https://github.com/sumpalabs/petrodb --skill tdd-sumpalabs
This Skill solves the common pain points of writing brittle tests that break during code refactors, building unverified features that introduce bugs, and maintaining low-value test suites that don't catch real behavior changes. It reduces rework and production issues by enforcing behavior-focused testing practices.
Use the tdd skill to write a failing test for the new user password reset feature before implementing any supporting code.
High-intent search queries and answers about installing and using this skill.
To write tests that survive refactoring, you must verify public API behavior instead of coupling tests to internal implementation details. This behavior-focused approach keeps your test suite stable during internal code changes.
The red-green-refactor cycle in test-driven development is a workflow where you write a failing test, implement minimal code to pass it, then safely refactor. This cycle ensures verified feature development and reduces production bugs.
Start test-first development by writing a single failing test for the new feature's behavior before implementing any supporting code. Then write the minimal code required to pass that test before safely refactoring the design.
Integration tests break during internal changes because they are likely coupled to implementation details rather than public behavior. Writing behavior-focused integration tests prevents this brittleness and reduces maintenance overhead.
A common test-driven development anti-pattern is horizontal slicing, where you write all tests before any implementation. This leads to low-value, fragile test suites that fail to verify behavior effectively.
Yes, test-driven development encourages deep module design by focusing tests on public behavior verification. This approach directly reduces your test surface area and minimizes long-term maintenance overhead.
patcarter883Collect goals, define requirements, and outline phases for the next development milestone.
RheasilviaEnforce the Red-Green-Refactor cycle with automated tests via terminal.
ysyecustVerify Spring Boot projects with builds, static analysis, tests, and security scans.
fcnatraCreate executable BDD specifications and scannable approval tests.
