Tdd Bugfix

TDD Bugfix

Test-first bug fix. Failing test proves the bug, fix makes it pass, runtime evidence confirms.

Do NOT use when

• No local test path exists (manual browser testing, production-only bugs)
• Building features (use architect-first then plan-slice)
• Refactoring (use deep-code-quality-review)

Workflow

1. Reproduce: Trace the code path to the defect. Write a minimal test that fails. Run it to confirm failure.
2. Root-cause: Follow root-cause checklist. Record root cause via ck_memory_record (type: finding).
3. Failing test: Write a test that demonstrates the bug. Must be: minimal, deterministic, clearly named. Confirm it fails.
4. Validate test: Run ck_validate on the test code. Fix findings.
5. Minimal fix: Smallest change to make the test pass. No refactoring, no improvements. Record improvement ideas via ck_memory_record for later.
6. Verify: Failing test passes. Full suite passes (mix test). Zero new failures.
7. Validate fix: Run ck_validate on the diff. Record findings.
8. Commit: ck_git_commit with message referencing the bug and test.

Rules

• Test first, fix second — no exceptions
• Minimal fix only — refactoring is a separate commit
• No Process.sleep/1 in tests — use monitors or :sys.get_state/1
• Root-cause, not symptom — fix the cause or record deeper issue as ck_finding

Output

• Failing test proving the bug
• Minimal fix making test pass
• Full suite passing
• Root cause recorded in memory