I agree with Rodrigo, it should be optional, but when the Rails Community takes its choice in supporting anything, it gets attention, people start to use it, and even the framework itself gets better.
Also, we really should ease the new developers life in pointing which framework to use when starting with rails and choosing the test frameworks. Everton On Thu, Sep 1, 2011 at 11: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?) > > 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. > > -- 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.
