I think due to the large number of testing frameworks out there for JavaScript, we should leave this in the developer's hands and not make it a part of the Rails core.
On 31/08/2011, at 23:06, Rodrigo Rosenfeld Rosas <[email protected]> wrote: > Hi guys, > > While reading the 3.1 release notes in Rails Guides, I've stumbled across > this phrase: > > "The major change in Rails 3.1 is the Assets Pipeline. It makes CSS and > JavaScript first-class code citizens and enables proper organization, > including use in plugins and engines." > > Then, I started thinking that it might not be really true. I guess, that it > is time for Rails to adopt a default testing framework for Javascript (both > unit and integration). > > There should also exist a Javascript generator that would generate the empty > test file too. It would also be interesting if we could generate views with > "--include-javascript", which would include a new file, like, for instance, > with jQuery: > > jQuery(function($){ > // place your code here. > }) > > Is there already something like this in Rails? I don't remember reading > anything about Javascript TDD natively with Rails. > > It seems like Capybara has became the defacto solution for this kind of test. > Maybe it could be the default Javascript test framework (using webkit by > default, maybe). > > Any thoughts? > > Cheers, > > Rodrigo. > > -- > 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.
