Select and apply London mock-based or Chicago state-based TDD styles.
npx skills add https://github.com/pacphi/ampel --skill tdd-london-chicago
Please help me install this Agent Skill. Skill: tdd-london-chicago Source: https://github.com/pacphi/ampel/tree/main/.claude/skills/tdd-london-chicago Command: npx skills add https://github.com/pacphi/ampel --skill tdd-london-chicago
This Skill eliminates testing confusion by clearly distinguishing between London school's interaction verification and Chicago school's state verification.
When implementing TDD: identify code type (domain logic → Chicago, external deps → London).
Write a failing test for "Order calculates total with tax" using Chicago style state verification.
High-intent search queries and answers about installing and using this skill.
London school uses mocks to verify how objects interact with dependencies, while Chicago school tests observable behavior through real objects and state verification. Choose London for code with external dependencies, Chicago for domain logic.
Write a failing test first (red), implement minimal code to pass it (green), then improve the code without breaking tests (refactor). The cycle builds confidence by validating each step before moving forward.
Use mocks in London-style TDD when testing interactions with external dependencies like APIs or databases. Use real objects in Chicago-style TDD to verify domain logic and state changes through your public API.
Yes. TDD works during refactoring by keeping tests green while you restructure code. Write tests for current behavior first, then refactor incrementally while verifying tests still pass.
Distinguish between London's interaction verification and Chicago's state verification upfront, assign clear test roles across implementation phases, and practice the red-green-refactor discipline consistently.
haitao2016Run unit tests for UrhoX Lua game units with assertions and mocks.
StrategicMilkIdentify untested code paths and generate test specifications with a JSON report.
Haohao-endImplement a red-green-refactor workflow to drive test-driven development.
AsiaOstrichGuide teams through ATDD workflows with Given-When-Then acceptance criteria.
