turkan wrote in post #961947: >> In your Cucumber stories, of course! > > But even in Cucumber you have to implement that somehow, or?
Right. > I don't know much about Cucumber as I do use Steak as mentioned, but I > am pretty sure that there is a way to do that there, too. I hadn't heard of Steak before. A quick look at the rdoc makes me think it's basically an inferior version of Cucumber. :) It looks to me like the author of Steak kind of missed the point that the English-like syntax of Cucumber is usually an advantage. > >> Controller and integration tests are needlessly painful. Skip them. >> Use Cucumber. > > So you don't test your controllers at all? I do test them, but only by means of my Cucumber stories. There's no reason to write conventional tests for controllers. > What do you mean by > integration test are painful. The integration testing interface provided by Test::Unit and RSpec is difficult to use and brittle. You couldn't pay me enough to touch it. > What are Cucumber tests then? A non-painful way to cover the same ground as integration tests. Best, -- Marnen Laibow-Koser http://www.marnen.org mar...@marnen.org Sent from my iPhone -- 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 post to this group, send email to rubyonrails-t...@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.
