Tdd Red Green Refactor

TDD Red / Green / Refactor

Use this skill whenever making code changes that should be covered by tests.

Non-negotiables

• Start with a failing test that expresses the behavior (red).
• Implement the smallest change to pass (green).
• Refactor for clarity/structure after green, keeping tests passing.
• If no tests exist, add a minimal test harness + a failing test first.

Workflow

1. Identify the smallest observable behavior.
2. Add or update a test to fail on current code.
3. Run the smallest relevant test command (targeted if possible).
4. Implement the minimal code to make it pass.
5. Refactor with tests still green.
6. Report: test command(s) run + results.

If tests cannot run

• State why (missing deps, env, credentials, etc.).
• Still write the failing test first and note the expected outcome.
• Provide a suggested test command for the user to run.

Test targeting

Prefer the narrowest scope:

• single file
• package-level
• repo-level only if needed

Typecheck policy

Types always pass. Do not blame pre-existing errors. Fix or revert.

WE USE VITEST - NOT BUN:TEST

This is non-negotiable. Never use bun:test imports or APIs.

// ✅ CORRECT - Vitest
import { describe, it, expect, vi, beforeEach } from 'vitest'

// ❌ WRONG - bun:test (DO NOT USE)
import { describe, it, expect, mock } from 'bun:test'

Test commands

# All tests via Turborepo
bun run test

# Filtered by package
bun run test --filter=@skillrecordings/core
bun run test --filter=web

# Direct Vitest (when you need fine-grained control)
bun run test:all
bun run test:all -- -t "name of test"
bun run test:all -- packages/core/src/tools/process-refund.test.ts

Common Vitest patterns

// Mocking
const mockFn = vi.fn()
vi.mocked(someModule).someMethod.mockResolvedValue(result)

// Hoisting mocks (required for factory functions)
const mockClient = vi.hoisted(() => ({ method: vi.fn() }))
vi.mock('./client', () => ({ client: mockClient }))

// Spying
vi.spyOn(object, 'method').mockImplementation(...)

Notes to include in the response

• Which test you wrote first.
• The command used to hit red and green.
• Any refactor that changed structure but not behavior.