On Tue, Apr 20, 2010 at 2:05 PM, David Chelimsky <dchelim...@gmail.com> wrote: > > On Apr 20, 2010, at 1:57 PM, Mike Sassak wrote: > >> On Tue, Apr 20, 2010 at 2:33 PM, Ed Howland <ed.howl...@gmail.com> wrote: >>> Please forgive the x-post. >>> >>> I just got back from the Great Lakes Ruby Bash. They had several good >>> presentations, two specific to BDD and Cucumber. I also talked to >>> several CEOs and devs afterwards, and the overall takeaway I gathered >>> was a shift to less RSpec and more Cucumber. Some people even claimed >>> a 90/10 split (cukes/specs) on current projects. >>> >>> This was surorising to me and not at all how I worked up to this >>> point. I was more 20/80. I usually cuked a feature, then spec'ed the >>> code to make the cuke work. Each release had some new features and >>> specs for all the underlying code. Apparently, the feeling is that you >>> should do all your main thrusts with Cucumber and use RSpec for edge >>> cases. The theory is that you can change out all the underlying code >>> and the cukes still pass. >>> >>> What is the communities consensus on this? >>> >> >> Hi Ed, >> >> I was also at the GLRB, and was a bit aghast at the claim that you >> should have a 90/10 split between cukes and rspec. In my experience, >> favoring Cucumber so heavily invites developing code that behaves >> correctly, but is messy and difficult to change. I would go so far as >> to claim there is a positive correlation between over-reliance on >> Cucumber features and rampant violations of the SOLID principles. >> Cucumber simply doesn't excel at enforcing simple, testable contracts >> between the objects in your code base the way RSpec does. The result >> is that your code is hard to refactor and change, which from the >> developer's point of view is practically the whole reason to maintain >> a good test suite in the first place. This isn't the whole of the >> story by any means, but I think it's close to the place to start. >> >> $0.02 >> Mike >> >> P.S. Hello RSpec Group! What's the etiquette here for cross-posting? > > Etiquette, schmetiquette :) > > I'd say, in the interest of keeping the thread in one place, post to the > rspec list w/ a link to this thread in the cuke group and invite folks to > join the convo.
I answered this before I realized you were already x-posting :) I think this conversation is relevant to both communities, so let's keep it going in both. > > Cheers, > David > >> >>> >>> Cheers, >>> Ed >>> >>> Ed Howland >>> http://greenprogrammer.wordpress.com >>> http://twitter.com/ed_howland >>> >>> -- >>> You received this message because you are subscribed to the Google Groups >>> "Cukes" group. >>> To post to this group, send email to cu...@googlegroups.com. >>> To unsubscribe from this group, send email to >>> cukes+unsubscr...@googlegroups.com. >>> For more options, visit this group at >>> http://groups.google.com/group/cukes?hl=en. >>> >>> >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Cukes" group. >> To post to this group, send email to cu...@googlegroups.com. >> To unsubscribe from this group, send email to >> cukes+unsubscr...@googlegroups.com. >> For more options, visit this group at >> http://groups.google.com/group/cukes?hl=en. >> > > _______________________________________________ rspec-users mailing list rspec-users@rubyforge.org http://rubyforge.org/mailman/listinfo/rspec-users
