Ruby on Rails

daze wrote in post #970911:
[...]
> Thing is, nowhere in my application is there a call of response_code!
> The error lies in the paginate method - an error revealed by browsing
> after doing rails server, NOT by testing! If testing had told me the
> paginate method was undefined, I would be satisfied.

Was there a stack trace?

>
> In any case.. the better error reporting in cucumber/rspec will
> hopefully quell these concerns.

I would think so.

>
> I'll get back to you on how the rspec + cucumber works out. I've been
> reading the background of cucumber and I'll get them installed/running
> soon.... hopefully.
>
> I came across this though: webrat or capybara? I'm not sure which.
> Either seems fine? I think I'll just choose webrat...?

I'm not sure. I've been using Webrat since before Capybara existed. I
think Capybara is supposed to have some advantages over Webrat
(including better JavaScript integration, maybe?), so I might try it on
my next project. Do your research and pick.

Best,
-- 
Marnen Laibow-Koser
http://www.marnen.org
marnen@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-talk@googlegroups.com.
To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.