test-driven-development
Use when implementing any feature or bugfix, before writing implementation code
by obraFree
Description
Write tests first, watch them fail, then implement minimal code to pass. Follows the red-green-refactor cycle: write a failing test, verify it fails correctly, implement minimal code to pass, then refactor while keeping tests green. Requires deleting any production code written before tests exist; no exceptions for "reference" or "adaptation".…
Ratings & Reviews
No ratings yet
Be the first to rate test-driven-development.
People also visit
finishing-a-development-branch
Guides completion of development work by presenting clear options
brainstorming
Transform rough ideas into fully-formed designs through structured questioning
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior
test-driven-development FAQ
What is test-driven-development?
Write tests first, watch them fail, then implement minimal code to pass. Follows the red-green-refactor cycle: write a failing test, verify it fails correctly, implement minimal code to pass, then refactor while keeping tests green. Requires deleting any production code written before tests exist; no exceptions for "reference" or "adaptation".
Is test-driven-development free?
Yes. test-driven-development is free to use.
Do I need to download test-driven-development?
No. test-driven-development runs in your browser at github.com, so there's nothing to install.
Who makes test-driven-development?
test-driven-development is made by obra.
What are the best test-driven-development alternatives?
Popular alternatives to test-driven-development include finishing-a-development-branch, using-git-worktrees and artifacts-builder. See all test-driven-development alternatives