[rspec-users] Mocks? Really?

Scott Taylor mailing_lists at railsnewbie.com
Mon Dec 31 11:49:34 EST 2007

On Dec 29, 2007, at 5:46 PM, Francis Hwang wrote:

> I don't know if anyone else will find this thought useful, but:
> I think different programmers have different situations, and they
> often force different sorts of priorities. I feel like a lot of the
> talk about mocking -- particularly as it hedges into discussions of
> modeling, design as part of the spec-writing process, LoD, etc --
> implicitly assumes you want to spend a certain percentage of your
> work-week delineating a sensible class design for your application,
> and embedding those design ideas into your specs. At the risk of
> sounding like a cowboy coder I'd like to suggest that some situations
> actually call for more tolerance of chaos than others.
> I can think of a few forces that might imply this:
> - Team size. A bigger team means the code's design has to be more
> explicit, because of the limits of implicity knowledge team members
> can get from one another through everyday conversation, etc.
> - How quickly the business needs change. Designs for medical imaging
> software are likely to change less quickly than those of a consumer-
> facing website, which means you might have more or less time to tease
> out the forces that would lead you to an optimal design.

+1 - This helps my thought out a lot.  Thanks for the contributions,  
as always (this has been a great thread - from everyone involved).


More information about the rspec-users mailing list