Justin Smestad wrote: > Also this is not a gap in merb testing, this would land more on > webrat and rspec I believe.
Given it 'should render' do ... end, what do I write for the ellipses? If the render system is too coupled to the view to test (like I suspect it is in Rails), then it's a gap in testability. Jacques Crocker wrote: > I actually wouldn't mind having a nice and easy way to spec partials. > They wouldn't work well as acceptance tests of course, it would be > cool to be able to set some instance variables, and some partial > locals, run the generator, then spec the results using have_selector > to get a better sense of progress as you're building up something. One project at my day job is an in-house app that targets only Firefox. This gives us free rein with the Ajax Abuse. User actions force screen update that replace the contents of divs with new renderings of partials. This means testing the contents of partials, in isolation, is mission critical. > Would be a nice way to work and experient with form helpers, etc, and > pieces of your app in the middle of working on something without > having to think too deep about end to end testing. I also wrote an assert_javascript system that can intercept the Ajax JS in @response.body, extract its target string, evaluate this as XHTML, and then test _that_. The partial is isolated - except you must call the controller action to get it! > This shouldn't be difficult to do as a custom helper. I'll do some > research on it, and see if I cant some up with something to package as > a merb plugin. ktxbye! --Phlip --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
