RubyConf 2011 | 2011-09-29 | Gregory Moeck (@gregmoeck) | Slides
- Recommended as the best book on mocks: Growing Object-Oriented Software, Guided by Tests by Steve Freeman & Nat Pryce
- Common arguments against mocks
- They duplicate implementation
- They lead to brittle tests
- Mock objects + procedural programming = bad idea
- If you're doing traditional Rails development (which tends to follow more of a "procedural", do-this-and-then-do-that style), mock objects probably aren't for you