On Fri, Feb 10, 2012 at 3:03 PM, Walter McGinnis <[email protected]>wrote:
> > On Feb 10, 2012, at 2:27 PM, Jeremy Olliver <[email protected]> > wrote: > > > We've just setup Jenkins as CI yesterday, though this isn't the first > time we've used it, and it seems to be pretty good. > > I'm not a fan of plain language specifications myself, though am finding > on our current project that rspec syntax in combination with Capybara steps > (no cucumber) is very readable. I don't think it's feasible to get a BA to > write the acutal tests/specs personally, and if they only need to specify > what you're testing, not write it themselves, then sitting down with a > BA/tester and writing some specs then is a nice way to go. > > Here's more discussion about cutting out cucumber and using some helpers > for more helpful output when using rspec with capybara: > > > http://blog.railsware.com/2012/01/08/capybara-with-givenwhenthen-steps-in-acceptance-testing/ > > Haven't tried it myself. > I'll take the opposite tack and say that clicking buttons, etc might be closer to how one developer would think, but there is value in abstracting the steps out into something a user actually does. Aslak says it better: http://aslakhellesoy.com/post/11055981222/the-training-wheels-came-off -- Best regards, Y. Thong Kuah http://kuahyeow.com -- You received this message because you are subscribed to the Google Groups "WellRailed" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/wellrailed?hl=en.
