On Sep 1, 10:30 am, Chad Woolley <[email protected]> wrote: > On Thu, Sep 1, 2011 at 6:40 AM, Michael Breen <[email protected]> wrote: > > Rails doesn't really ship with any testing framework. It defaults to what's > > in Ruby core, which is Test/Unit in 1.8 and MiniTest in 1.9. > > * Rails ships with Ruby test generators (because testing is good) > * Rails ships with Javascript/Coffeescript generators > * There's no Javascript testing framework in Ruby core, nor Rails. > (testing is only good for Ruby code?)
I wasn't trying to say that Rails shouldn't encourage Javascript testing. But the fact that Rails does not ship a testing framework and, out of the box, encourages you to use the testing framework that is already on your machine should be noted. I can't recall ever seeing 3000+ word blog posts on getting Test/Unit to work with Rails as I have for other testing frameworks. Ruby core may never include a Javascript testing framework but maybe this shouldn't be decided by a bunch of +1's on a thread right now. Since some of these features/tools are new to Rails maybe the best thing to do (as others have noted) is to see how the JS testing frameworks adapt and evolve before forming an opinion? > > One of Rails' many opinionated innovations as a framework was that > testing is good, everyone should do it by default, so test code is > included/generated by the framework. I believe it should be just as > opinionated about Javascript testing. > > As Rodrigo said, it doesn't matter which framework is used (although > Jasmine is nice and iterates/improves upon several earlier tools). The > important thing is to send the message that Javascript can and should > be tested. > > -- Chad -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" 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/rubyonrails-core?hl=en.
