Interesting. Webrat is required for testing, but it shouldn't have been
required for merb -i. We should get some docs on the wiki about how to get
webrat up and running on platforms that have more complex nokogiri
requirements.
The rationale for using webrat for testing, btw, was to provide a very good,
integrated solution for testing that worked well with Merb's request spec
helpers. As a result, you can easily do things like:
request("/some/path")
resp = click_link("Some link")
resp.should have_selector("p:contains(foo)")
fill_in "Label Text", :with => "Contents"
resp = click_button "Button Text"
resp.should have_selector("h1:contains(Success)")
Using nokogiri should make these sorts of tests fast and efficient, and
using rspec should allow you to easily divide the tests (using rspec's
nested contexts) so you can have many scenarios that use shared setup logic.
Out of curiosity, what version of Rubygems are you running?
-- Yehuda
On Mon, Nov 10, 2008 at 7:12 AM, mike jones
<[EMAIL PROTECTED]>wrote:
>
> Already a know bug I see
>
>
> http://merb.lighthouseapp.com/projects/7433/tickets/986-webrat-is-required-for-merb-core-app-running-in-console#ticket-986-6
>
> On Nov 10, 11:44 am, mike jones <[EMAIL PROTECTED]>
> wrote:
> > It seems so because the tests wont run with out it buts its not
> > installed when install merb.
> > Cheers
> > Mike
> >
>
--
Yehuda Katz
Developer | Engine Yard
(ph) 718.877.1325
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"merb" 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/merb?hl=en
-~----------~----~----~----~------~----~------~--~---
