tdd-london-chicago

Name: tdd-london-chicago
Availability: InStock
Author: summarybotng

Compare London and Chicago Test-Driven Development schools with code examples.

2|2|Updated Aug 23, 2025

Search Tags:#testing #tdd #refactoring #unit testing #london school #chicago school

Ready to run

npx skills add https://github.com/summarybotng/summarybot-ng --skill tdd-london-chicago-summarybotng

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: tdd-london-chicago
Source: https://github.com/summarybotng/summarybot-ng/tree/main/.claude/skills/tdd-london-chicago
Command: npx skills add https://github.com/summarybotng/summarybot-ng --skill tdd-london-chicago-summarybotng

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps developers understand and apply the principles of Test-Driven Development (TDD) by clearly differentiating between the London (mock-based) and Chicago (state-based) schools of thought, enabling better testing strategies.

Core Features & Use Cases

TDD School Comparison: Detailed explanations and code examples for both London and Chicago TDD approaches.
Practical Guidance: Advice on when to use each school and how to mix them effectively.
Agent Coordination: Demonstrates how AI agents can assist in the Red-Green-Refactor cycle.
Use Case: When starting a new feature, use this Skill to decide whether to focus on testing object interactions (London) or verifying final state (Chicago) for your specific code.

Quick Start

Use the tdd-london-chicago skill to understand the difference between state-based and interaction-based testing.

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 schools in TDD?▼

London TDD focuses on interaction-based testing using mocks to verify object behavior, while Chicago TDD applies state-based testing to verify the final output of the system.

When should I use mock-based testing instead of state-based testing?▼

Use mock-based testing to isolate object interactions and define system boundaries, and use state-based testing to verify the final state of the system.

How do I apply the red-green-refactor cycle using TDD methodologies?▼

Apply the red-green-refactor cycle by writing a failing test, implementing code to pass it, and refactoring, using AI agent coordination strategies to assist in the process.

Can I mix London and Chicago TDD approaches in my unit testing strategy?▼

Yes, you can mix London and Chicago TDD approaches by applying a mixed-approach recommendation that selects interaction-based or state-based testing based on specific use cases.

What are common pitfalls when doing Test-Driven Development?▼

Common pitfalls in Test-Driven Development include choosing the wrong testing school for your context and failing to properly execute the red-green-refactor cycle, which this guidance addresses.