testing-tdd-london-london-vs-chicago-school

Sub-skill of testing-tdd-london: London vs Chicago School (+2).

5 stars

Best use case

testing-tdd-london-london-vs-chicago-school is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

Sub-skill of testing-tdd-london: London vs Chicago School (+2).

Teams using testing-tdd-london-london-vs-chicago-school should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

You only need a quick one-off answer and do not need a reusable workflow.
You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/london-vs-chicago-school/SKILL.md --create-dirs "https://raw.githubusercontent.com/vamseeachanta/workspace-hub/main/.agents/skills/_archive/development/testing/testing-tdd-london/london-vs-chicago-school/SKILL.md"

Manual Installation

Download SKILL.md from GitHub
Place it in .claude/skills/london-vs-chicago-school/SKILL.md inside your project
Restart your AI agent — it will auto-discover the skill

How testing-tdd-london-london-vs-chicago-school Compares

Feature / Agent	testing-tdd-london-london-vs-chicago-school	Standard Approach
Platform Support	Not specified	Limited / Varies
Context Awareness	High	Baseline
Installation Complexity	Unknown	N/A

Frequently Asked Questions

What does this skill do?

Sub-skill of testing-tdd-london: London vs Chicago School (+2).

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

SKILL.md Source

# London vs Chicago School (+2)

## London vs Chicago School


| Aspect | London (Mockist) | Chicago (Classicist) |
|--------|------------------|----------------------|
| Focus | Behavior/Interactions | State |
| Isolation | Mock all collaborators | Use real objects |
| Direction | Outside-in | Inside-out |
| Test What | HOW objects talk | WHAT objects produce |
| Coupling | To implementation | To behavior |

## Outside-In Development Flow


```
Acceptance Test (failing)
    |
    v
Controller Test (failing)
    |
    v
Service Test (failing)
    |
    v
Repository Test (failing)
    |
    v
Implement (make tests pass from bottom up)
```

## Mock Types


```typescript
// Stub: Returns canned responses
const stubRepo = { findById: jest.fn().mockResolvedValue(user) };

// Mock: Verifies interactions
const mockNotifier = { send: jest.fn() };
// Later: expect(mockNotifier.send).toHaveBeenCalledWith(expectedArgs);

// Spy: Wraps real object, records calls
const spyLogger = jest.spyOn(logger, 'info');
```

Related Skills

webapp-testing

from vamseeachanta/workspace-hub

Web application testing toolkit using Playwright with Python. Use for verifying frontend functionality, debugging UI behavior, capturing browser screenshots, viewing browser logs, and automating web interactions.

testing-tdd-london

from vamseeachanta/workspace-hub

TDD London School (mockist) specialist for mock-driven, outside-in development. Use for behavior verification testing, contract-driven development, testing object collaborations, or when focusing on HOW objects interact rather than WHAT they contain.

testing-production

from vamseeachanta/workspace-hub

Production validation specialist ensuring applications are fully implemented and deployment-ready. Use to verify no mock/stub/fake implementations remain, validate against real databases and APIs, perform end-to-end testing with actual systems, and confirm production readiness.