On Wed, Oct 29, 2008 at 10:32 PM, David Chelimsky <[EMAIL PROTECTED]> wrote: > On Tue, Oct 28, 2008 at 2:32 AM, Ashley Moran > <[EMAIL PROTECTED]> wrote: >> >> On Oct 27, 2008, at 5:20 pm, Pat Maddox wrote: >> >>> When it comes to controllers specs, mocks provide the most value by >>> isolating from the model and db - the specs run faster, and you don't >>> have to worry about model validations. But if you minimize controller >>> logic, you can write acceptance tests that give you confidence that >>> your controllers work, and then controller specs become unnecessary >>> overhead. >> >> >> What's the consensus here then, controller specs yay or nay? >> >> 1 nay from Pat >> >> 1 act of fence sitting from me... > > I think the nay from Pat was conditional, as it should be. > > I think the answer is: if you have to ask, then you should use them :) > Otherwise, don't use them when you feel confident that you don't need > them. >
When working outside in, the granularity increases the further in you get. On the very outside it's cumbersome to test for edge cases. Start on the outside with Cucumber and whenever you come across an edge case, make a judgement on where the right abstraction level is to test it. That may be controller, view, model or somewhere else. Don't write specs just cuz Aslak > FWIW, > David > >> >> Ashley >> >> -- >> http://www.patchspace.co.uk/ >> http://aviewfromafar.net/ >> >> _______________________________________________ >> rspec-users mailing list >> rspec-users@rubyforge.org >> http://rubyforge.org/mailman/listinfo/rspec-users >> > _______________________________________________ > rspec-users mailing list > rspec-users@rubyforge.org > http://rubyforge.org/mailman/listinfo/rspec-users > _______________________________________________ rspec-users mailing list rspec-users@rubyforge.org http://rubyforge.org/mailman/listinfo/rspec-users
