ring%3atest-driven-development（Ring%3 最驱动的开发）

Test-Driven Development (TDD)

Overview

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.

When to Use

Always:

• New features
• Bug fixes
• Refactoring
• Behavior changes

Exceptions (ask your human partner):

• Throwaway prototypes
• Generated code
• Configuration files

Thinking "skip TDD just this once"? Stop. That's rationalization.

The Iron Law

NO PRODUCTION CODE WITHOUT A FAILING TEST FIRST

Write code before the test? You have ONLY two options:

Violation Handling (Mandatory)

If you wrote code before test:

DELETE IT. IMMEDIATELY.

rm [files]  # or git reset --hard

Not tomorrow. Not after asking. NOW.

Delete means DELETE:

• rm -rf the_file.py ✓
• git reset --hard ✓
• Physically delete ✓

These are NOT deleting (violations):

• git stash - That's hiding, not deleting
• mv file.py file.py.bak - That's keeping
• Copy to clipboard - That's keeping
• Comment out - That's keeping
• "Mental note" - That's keeping
• Asking permission - That's delaying

Delete means gone forever. No recovery possible.

Then start over with TDD.

NO ASKING. NO PERMISSION. NO EXCEPTIONS.

You CANNOT:

• ❌ Ask "should I delete this?"
• ❌ Ask "may I proceed with tests-after?"
• ❌ Request permission due to [any reason]
• ❌ Explain why deleting is hard
• ❌ Decide "I'll be pragmatic and test after"
• ❌ Claim "spirit not letter"
• ❌ Rationalize "damage already done"
• ❌ Argue "skill is guide not suicide pact"
• ❌ Create "pragmatic compliance" category
• ❌ Mention sunk cost, time pressure, personal plans
• ❌ Commit anything

If you think you have a legitimate reason to skip deletion:

• You don't.
• Delete it.
• Every excuse is rationalization.
• Anniversary? Delete code, go to dinner, start fresh tomorrow.
• Deadline? Delete code, communicate delay, do it right.
• 4 hours of work? Sunk cost fallacy. Delete it.
• Manager pressure? Delete it, explain TDD prevents bugs.
• "But this is different because..." No. Delete it.

The rule has ZERO exceptions. ZERO.

Consequences of NOT Deleting

Untested code WILL cause production incidents. These are CERTAINTIES:

• Trust: Partner loses confidence permanently. PRs rejected. Assigned bug duty.
• Production: Incident within 30 days. Worst timing (holiday, 3am). Postmortem responsibility.
• Career: Reputation as "cuts corners" follows you. Promotion blocked.
• Personal: Anniversary debugging. Technical debt haunts for years.

❌ "This time is different" → Every developer who thought this experienced these consequences.

The ONLY Acceptable Action

DELETE THE CODE. NOW.

rm /tmp/auth-feature/src/auth.ts
rm /tmp/auth-feature/src/middleware.ts
rm /tmp/auth-feature/src/utils.ts
# or: git reset --hard

Then:

• Go to anniversary dinner
• Sleep well
• Tomorrow morning: Start fresh with TDD
• Implement in 2-3 hours with tests (faster second time)
• Code review passes
• No production incidents
• Career intact

ZERO exceptions. Anniversary, deadline, manager pressure, sunk cost - NONE of these override deletion.

Prohibited Rationalizations

You CANNOT create alternatives:

• ❌ "Commit with WIP message" - NO. Delete.
• ❌ "Commit with 'NO TESTS' warning" - NO. Delete.
• ❌ "Mark as technical debt" - NO. Delete.
• ❌ "Email team about violation" - NO. Delete first, communicate after.
• ❌ "Come early tomorrow to decide" - NO. Delete now, decide nothing.
• ❌ "Let team decide" - NO. You decide: Delete.
• ❌ "Write tests tonight after dinner" - NO. Delete, start fresh tomorrow with TDD.
• ❌ "Commit honestly labeled code" - NO. Honesty is deleting it.
• ❌ "Present options to partner" - NO. Only one option: Delete.

The skill doesn't offer choices. It commands: DELETE.

If you create ANY alternative to deletion, you violated the skill.

DELETE IT. NOW. NO ALTERNATIVES.

Red-Green-Refactor

Cycle: RED (write failing test) → verify fails → GREEN (minimal code) → verify passes → REFACTOR (clean up) → verify still green → repeat

RED - Write Failing Test

Write one minimal test showing what should happen.

GOOD: test('retries failed operations 3 times',...) - clear name, tests real behavior, one thing.

BAD: test('retry works',...) with mocks - vague name, tests mock not code.

Time limit: <5 minutes. Complex mocks → testing wrong thing. Lots of setup → design too complex. Multiple assertions → split tests.

Requirements:

• One behavior
• Clear name
• Real code (no mocks unless unavoidable)

Verify RED - Watch It Fail

MANDATORY. Never skip.

npm test path/to/test.test.ts

Paste the ACTUAL failure output in your response:

[PASTE EXACT OUTPUT HERE]
[NO OUTPUT = VIOLATION]

If you can't paste output, you didn't run the test.

Required Failure Patterns

No failure output = didn't run = violation

Confirm:

• Test fails (not errors)
• Failure message is expected
• Fails because feature missing (not typos)

Test passes? You're testing existing behavior. Fix test.

Test errors? Fix error, re-run until it fails correctly.

GREEN - Minimal Code

Write simplest code to pass the test.

GOOD: Simple loop with try/catch, just enough to pass. BAD: Adding options, backoff, callbacks (YAGNI).

Don't add features, refactor other code, or "improve" beyond the test.

Verify GREEN - Watch It Pass

MANDATORY.

npm test path/to/test.test.ts

Confirm:

• Test passes
• Other tests still pass
• Output pristine (no errors, warnings)

Test fails? Fix code, not test.

Other tests fail? Fix now.

REFACTOR - Clean Up

After green only:

• Remove duplication
• Improve names
• Extract helpers

Keep tests green. Don't add behavior.

Repeat

Next failing test for next feature.

Good Tests

Why Order Matters

Common Rationalizations

Red Flags - STOP and Start Over

• Code before test
• Test after implementation
• Test passes immediately
• Can't explain why test failed
• Tests added "later"
• Rationalizing "just this once"
• "I already manually tested it"
• "Tests after achieve the same purpose"
• "It's about spirit not ritual"
• "Keep as reference" or "adapt existing code"
• "Already spent X hours, deleting is wasteful"
• "TDD is dogmatic, I'm being pragmatic"
• "This is different because..."

All of these mean: Delete code. Start over with TDD.

Example: Bug Fix

Bug: Empty email accepted → RED: test('rejects empty email',...) → Verify RED: FAIL: expected 'Email required', got undefined → GREEN: Add if (!data.email?.trim()) return {error: 'Email required'} → Verify GREEN: PASS → REFACTOR: Extract validation if needed.

Verification Checklist

Before marking work complete:

• Every new function/method has a test
• Watched each test fail before implementing
• Each test failed for expected reason (feature missing, not typo)
• Wrote minimal code to pass each test
• All tests pass
• Output pristine (no errors, warnings)
• Tests use real code (mocks only if unavoidable)
• Edge cases and errors covered

Can't check all boxes? You skipped TDD. Start over.

When Stuck

Debugging Integration

Bug found? Write failing test reproducing it. Follow TDD cycle. Test proves fix and prevents regression.

Never fix bugs without a test.

Required Patterns

This skill uses these universal patterns:

• State Tracking: See skills/shared-patterns/state-tracking.md
• Failure Recovery: See skills/shared-patterns/failure-recovery.md
• Exit Criteria: See skills/shared-patterns/exit-criteria.md
• TodoWrite: See skills/shared-patterns/todowrite-integration.md

Apply ALL patterns when using this skill.

Violation Recovery Quick Reference

Why recovery matters: Test must fail first to prove it tests something. Keeping code means you'll adapt it instead of implementing from tests.

Final Rule

Production code → test exists and failed first
Otherwise → not TDD

No exceptions without your human partner's permission.

Blocker Criteria

STOP and report if:

Cannot Be Overridden

The following requirements CANNOT be waived:

• MUST write test before implementation code
• MUST watch test fail before writing implementation
• MUST DELETE any code written before its test
• MUST NOT stash, backup, or keep "reference" of untested code
• MUST verify test fails for the right reason (missing feature, not typo)

Severity Calibration

Pressure Resistance

Anti-Rationalization Table