On Tue, Aug 5, 2008 at 10:12 AM, David Chelimsky <[EMAIL PROTECTED]> wrote: > On Sat, Aug 2, 2008 at 6:49 PM, Luis Lavena <[EMAIL PROTECTED]> wrote: >> Hello list, >> >> I'm trying to setup some shared specs to describe a CRUD controller >> and want to reuse the logic in it. >> >> I'm basing most of the examples in latest David's post about it [1] >> >> The thing is that looking at the mailing list I couldn't find a >> cleaner way to set the model that will be used in the different >> controller examples. >> >> Has anyone experienced DRY without removing readability in this topic? > > I think it's ironic that you cite my post about the goodness of being > less DRY in your quest for more DRY-ness. ;) >
Thanks I always give my best :-D >> I was looking for something like this: >> >> describe Invoices do >> it_should_behave_like "CRUD", :model => Invoice, ... >> end > > There is an open ticket on this: http://rubyurl.com/7ZsP > > Please feel free to resurrect the conversation there. > Thanks for the pointer, but after further review of my code (and a complete weekend to think about it) I'll stick to a before :each that set the @model_class. The quest to find balance between DRY and readability is the hardest one. > Cheers, > David > Thanks David for your time answering this email. Regards, -- Luis Lavena AREA 17 - Human beings, who are almost unique in having the ability to learn from the experience of others, are also remarkable for their apparent disinclination to do so. Douglas Adams _______________________________________________ rspec-users mailing list rspec-users@rubyforge.org http://rubyforge.org/mailman/listinfo/rspec-users
