test-driven-development

Topics in the source

• Test-Driven Development (TDD)
• Overview
• When to Use
• The Iron Law
• Red-Green-Refactor
• RED - Write Failing Test
• Verify RED - Watch It Fail
• GREEN - Minimal Code

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. Violating the letter of the rules is violating the spirit of the rules. Always: New features Bug fixes Refactoring Behavior changes Exceptions (ask the user first): Throwaway prototypes Generated code Configuration files Thinking "skip TDD just this once"? Stop. That's rationalization. No test setup in the project? Use the smallest runner the stack already ships (node --test, python -m unittest, go test, cargo test), put the test next to the existing code's conventions, and tell the user you added it. Installing a runner such as pytest is a new dependency: ask first. Wrote production code in this task before its test? Delete it. Start over. No exceptions: Don't keep it as "reference" Don't "adapt" it while writing tests Don't look at it Delete means delete Implement fresh from tests. Period. Write one minimal test showing what should happen. Clear name, tests real behavior, one thing Vague name, tests mock not code Requirements: One behavior Clear name Real code (no mocks unless unavoidable) MANDATORY. Never skip. npm test h

This is an excerpt. Refer to the complete source and its current requirements.