tdd-london-chicago

Coordinate agent-assisted TDD guidance blending London and Chicago testing styles.

Updated Jan 4, 2026
One-click install
npx skills add https://github.com/natea/ai-news-influencer --skill tdd-london-chicago-natea
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tdd-london-chicago
Source: https://github.com/natea/ai-news-influencer/tree/main/.claude/skills/tdd-london-chicago
Command: npx skills add https://github.com/natea/ai-news-influencer --skill tdd-london-chicago-natea

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Teams practicing test-driven development often struggle to choose and apply the right TDD strategy. This Skill guides practitioners to blend London (mock-based) and Chicago (state-based) testing approaches for more effective design and reliable tests.

Core Features & Use Cases

  • Guided TDD Cycle: Supports Red-Green-Refactor workflows across both schools, with clear transitions between mock-based and state-based testing.
  • Dual-Style Selection: Helps determine when to apply mocks vs real objects based on domain boundaries and dependencies.
  • Agent Coordination: Orchestrates task delegation among agents (qe-test-generator, qe-test-implementer, qe-test-refactorer) to generate, implement, and refactor tests.
  • Educational Scenarios: Useful for teaching teams TDD philosophy and for refactoring legacy code with proper test coverage.

Quick Start

Describe how to apply London and Chicago TDD styles to a new feature in your codebase to practice TDD effectively.

Frequently Asked Questions about tdd-london-chicago

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is the difference between London and Chicago school TDD?

London school TDD uses mocks to verify interactions between objects, while Chicago school TDD uses real objects to verify state. Blending both approaches helps balance design feedback and test reliability across domain boundaries.

How do I know when to use mocks vs real objects in test-driven development?

Use mocks when testing interactions across domain boundaries with external dependencies, and use real objects for state-based testing within the domain. The Skill guides this selection based on dependency boundaries to improve test quality.

How do I apply red-green-refactor cycles when blending London and Chicago TDD styles?

Run red-green-refactor cycles by writing a failing test, implementing minimal code to pass, then refactoring. The Skill coordinates transitions between mock-based and state-based testing throughout the cycle to guide design decisions.

Can I use test-driven development to refactor legacy code without existing test coverage?

Yes, the Skill supports refactoring legacy code by applying blended TDD styles to build proper test coverage. It guides mock and real object selection to safely introduce tests around existing domain boundaries.

Does this TDD approach work for teaching teams test-driven development philosophy?

Yes, the Skill includes educational scenarios designed for teaching teams TDD philosophy. It demonstrates when to apply London or Chicago styles to improve collective understanding of test quality and design decisions.

What is the best way to coordinate agents for generating and refactoring tests in TDD?

The Skill orchestrates task delegation among qe-test-generator, qe-test-implementer, and qe-test-refactorer agents to generate, implement, and refactor tests within blended London and Chicago TDD workflows.