I'd recommend learning RSpec first, as Cucumber is an additional abstraction above. Think of it this way:
RSpec: reads more like code, but you can see exactly which methods are being called, etc. Cucumber: reads more like English, but you have to maintain a file to "translate" from the code Cucumber is often used when interacting with clients who don't necessarily know how to code, as they will be able to understand the plain language and can even help create some of the tests themselves. On Wednesday, May 23, 2012 1:05:55 PM UTC-7, Ruby-Forum.com User wrote: > > Thank you for this very useful reply, Robert. > > I decided to go with the RSpec book now, because from its foreword I can > tell that it's not only about RSpec, but it's also about Cucumber (and > many other accompanying tools, too), so I'm quite confident I will get a > good introduction in both tools and will know which one I want to use > (or even both). > > And you're right about the date of the book - the basic ideas don't > happen to change that fast, and it won't be too tricky to catch up with > the new features after I grasped the basic concepts. > > Thanks again, I'm confident that I'm on a good way now! > > -- > Posted via http://www.ruby-forum.com/. > -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To view this discussion on the web visit https://groups.google.com/d/msg/rubyonrails-talk/-/zwcu8atIMlAJ. To post to this group, send email to rubyonrails-talk@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-talk+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
