Self-hosted alternatives to test-driven-development

T

test-driven-development

Use when implementing any feature or bugfix, before writing implementation code

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".