On 19.01.2009, at 7:45, Phlip wrote:
> Webrat is going to... what? grab your web server, on this side of > the HTTP, make > it build real Request and Response objects (or their equivalents), > run the web > server to process one action, and return the results in a big string? > why don't you just have a look at the source? I said earlier that Webrat does not do any http requests, it wraps merb's request helper method > Or is it lower level, and it's just Merb's test-side 'get'? webrat is very high level, you operate terms like "click a link", "fill in form field", "submit form", "attach file" and not get/post/put (though you still have access to them if you need them) with cucumber webrat tests are basically plain text where you write most of your test vocabulary during first 3-4 days of development and then to write tests you just copy-paste and edit text, rarely adding some Ruby code as you go another thing I fell in love about webrat is that you write real scenarios of what user can possibly do: go there, do that, see that other thing, then go to other place, do other thing, etc. Session is carried around, redirects are followed, Webrat respects cookies and lets you test larger chunks easily instead of working at lower level with separated requests that may work in isolation but do not work once integrated. And... I am still waiting for a stack trace. MK --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
