/context-mode-ops

Test-Driven Development

Source: mattpocock/skills/tdd — embedded with context-mode enforcement.

Philosophy

Core principle: Tests should verify behavior through public interfaces, not implementation details. Code can change entirely; tests shouldn't.

Good tests are integration-style: they exercise real code paths through public APIs. They describe what the system does, not how it does it. A good test reads like a specification — "user can checkout with valid cart" tells you exactly what capability exists. These tests survive refactors because they don't care about internal structure.

Bad tests are coupled to implementation. They mock internal collaborators, test private methods, or verify through external means (like querying a database directly instead of using the interface). The warning sign: your test breaks when you refactor, but behavior hasn't changed. If you rename an internal function and tests fail, those tests were testing implementation, not behavior.

Anti-Pattern: Horizontal Slices

DO NOT write all tests first, then all implementation. This is "horizontal slicing" — treating RED as "write all tests" and GREEN as "write all code."

This produces crap tests:

• Tests written in bulk test imagined behavior, not actual behavior
• You end up testing the shape of things (data structures, function signatures) rather than user-facing behavior
• Tests become insensitive to real changes — they pass when behavior breaks, fail when behavior is fine
• You outrun your headlights, committing to test structure before understanding the implementation

Correct approach: Vertical slices via tracer bullets. One test → one implementation → repeat. Each test responds to what you learned from the previous cycle. Because you just wrote the code, you know exactly what behavior matters and how to verify it.

WRONG (horizontal):
  RED:   test1, test2, test3, test4, test5
  GREEN: impl1, impl2, impl3, impl4, impl5

RIGHT (vertical):
  RED→GREEN: test1→impl1
  RED→GREEN: test2→impl2
  RED→GREEN: test3→impl3
  ...

Workflow

1. Planning

Before writing any code:

• Identify what behaviors need to change or be added
• List the behaviors to test (not implementation steps)
• Identify opportunities for deep modules (small interface, deep implementation)
• Design interfaces for testability

You can't test everything. Focus testing effort on critical paths and complex logic, not every possible edge case.

2. Tracer Bullet

For the first behavior:

RED:   Write test for first behavior → test fails
GREEN: Write minimal code to pass → test passes

Then refactor:

• Extract duplication
• Deepen modules (move complexity behind simple interfaces)
• Apply SOLID principles where natural
• Consider what new code reveals about existing code
• Run tests after each refactor step

Never refactor while RED. Get to GREEN first.

3. Next Behavior

RED:   Write next test → fails
GREEN: Minimal code to pass → passes

Refactor again. Repeat until all behaviors are covered.

Good and Bad Tests

Good Tests (Integration-Style)

// GOOD: Tests observable behavior
test("user can checkout with valid cart", async () => {
  const cart = createCart();
  cart.add(product);
  const result = await checkout(cart, paymentMethod);
  expect(result.status).toBe("confirmed");
});

Characteristics:

• Tests behavior users/callers care about
• Uses public API only
• Survives internal refactors
• Describes WHAT, not HOW
• One logical assertion per test

Bad Tests (Implementation-Coupled)

// BAD: Tests implementation details
test("checkout calls paymentService.process", async () => {
  const mockPayment = jest.mock(paymentService);
  await checkout(cart, payment);
  expect(mockPayment.process).toHaveBeenCalledWith(cart.total);
});

Red flags:

• Mocking internal collaborators
• Testing private methods
• Asserting on call counts/order
• Test breaks when refactoring without behavior change
• Test name describes HOW not WHAT
• Verifying through external means instead of interface

// BAD: Bypasses interface to verify
test("createUser saves to database", async () => {
  await createUser({ name: "Alice" });
  const row = await db.query("SELECT * FROM users WHERE name = ?", ["Alice"]);
  expect(row).toBeDefined();
});

// GOOD: Verifies through interface
test("createUser makes user retrievable", async () => {
  const user = await createUser({ name: "Alice" });
  const retrieved = await getUser(user.id);
  expect(retrieved.name).toBe("Alice");
});

When to Mock

Mock at system boundaries only:

• External APIs (payment, email, etc.)
• Databases (sometimes — prefer test DB)
• Time/randomness
• File system (sometimes)

Don't mock:

• Your own classes/modules
• Internal collaborators
• Anything you control

Designing for Mockability

1. Use dependency injection

Pass external dependencies in rather than creating them internally:

// Easy to mock
function processPayment(order, paymentClient) {
  return paymentClient.charge(order.total);
}

// Hard to mock
function processPayment(order) {
  const client = new StripeClient(process.env.STRIPE_KEY);
  return client.charge(order.total);
}

2. Prefer SDK-style interfaces over generic fetchers

Create specific functions for each external operation instead of one generic function with conditional logic:

// GOOD: Each function is independently mockable
const api = {
  getUser: (id) => fetch(`/users/${id}`),
  getOrders: (userId) => fetch(`/users/${userId}/orders`),
  createOrder: (data) => fetch('/orders', { method: 'POST', body: data }),
};

// BAD: Mocking requires conditional logic inside the mock
const api = {
  fetch: (endpoint, options) => fetch(endpoint, options),
};

The SDK approach means:

• Each mock returns one specific shape
• No conditional logic in test setup
• Easier to see which endpoints a test exercises
• Type safety per endpoint

Interface Design for Testability

Good interfaces make testing natural:

1. Accept dependencies, don't create them

   // Testable
   function processOrder(order, paymentGateway) {}
   
   // Hard to test
   function processOrder(order) {
     const gateway = new StripeGateway();
   }

2. Return results, don't produce side effects

   // Testable
   function calculateDiscount(cart): Discount {}
   
   // Hard to test
   function applyDiscount(cart): void {
     cart.total -= discount;
   }

3. Small surface area

   • Fewer methods = fewer tests needed
   • Fewer params = simpler test setup

Deep Modules

From "A Philosophy of Software Design":

Deep module = small interface + lots of implementation

┌─────────────────────┐
│   Small Interface   │  ← Few methods, simple params
├─────────────────────┤
│                     │
│                     │
│  Deep Implementation│  ← Complex logic hidden
│                     │
│                     │
└─────────────────────┘

Shallow module = large interface + little implementation (avoid)

┌─────────────────────────────────┐
│       Large Interface           │  ← Many methods, complex params
├─────────────────────────────────┤
│  Thin Implementation            │  ← Just passes through
└─────────────────────────────────┘

When designing interfaces, ask:

• Can I reduce the number of methods?
• Can I simplify the parameters?
• Can I hide more complexity inside?

Refactor Candidates

After TDD cycle, look for:

• Duplication → Extract function/class
• Long methods → Break into private helpers (keep tests on public interface)
• Shallow modules → Combine or deepen
• Feature envy → Move logic to where data lives
• Primitive obsession → Introduce value objects
• Existing code the new code reveals as problematic

context-mode Specific Rules

CONTRIBUTING.md Is the Authority

Read CONTRIBUTING.md before writing any test. It defines:

• Test file organization (which file to put your test in)
• TDD workflow (Red-Green-Refactor)
• Output quality comparison (before/after)
• Local development setup

Do NOT create new test files. CONTRIBUTING.md has the complete test file mapping. Add your tests to the existing file that covers the same domain. If no file fits, ask the maintainer.

CI Builds Bundles — You Don't

Do NOT run npm run build or npm run bundle. Bundle files (server.bundle.mjs, cli.bundle.mjs) are generated by GitHub CI automatically. Never create, modify, or push bundle files. You only run:

npm test              # vitest — validates behavior
npm run typecheck     # tsc --noEmit — validates types

That's it. No build. No bundle. CI handles the rest.

TDD Enforcement in Subagents

Every Staff Engineer agent MUST include this in their prompt:

MANDATORY TDD — your work will be REJECTED without this:
1. Read CONTRIBUTING.md for test file organization — do NOT create new test files
2. Write a failing test FIRST in the correct existing test file
3. Run: npx vitest run tests/{file} — MUST FAIL
4. Write minimal code to pass
5. Run: npx vitest run tests/{file} — MUST PASS
6. Refactor if needed, tests stay green
7. Report RED→GREEN evidence:
   "RED:  test 'detects opencode via env var' — FAIL (expected)"
   "GREEN: added env check in detect.ts — PASS"
   Without this evidence, your PR is auto-rejected.