On Wed, Aug 31, 2011 at 3:10 PM, Wael Nasreddine
<wael.nasredd...@gmail.com> wrote:
> +1 too, jasmine for unit testing and capybara for integration tests
Wellllll… make Jasmine optional and I'm a happy camper :)
> Regards,
> Wael
>
> --
> Wael Nasreddine
> Sent from my iPhone
> On Aug 31, 2011, at 19:46, Everton Moreth <everton.mor...@gmail.com> wrote:
>
> A standard javascript testing library would be awesome.
>
> Today we struggle with lots of different aproaches to test javascript, using
> only selenium, capybara/selenium, cucumber/capybara/selenium, jasmine,
> etc... And other non Rails techniques. It would be great if we could rely
> and focus on a single framework to develop to and help.
>
> +1
>
> Everton Moreth
>
> On Wed, Aug 31, 2011 at 10:06 AM, Rodrigo Rosenfeld Rosas
> <rr.ro...@gmail.com> 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 rubyonrails-core@googlegroups.com.
>> To unsubscribe from this group, send email to
>> rubyonrails-core+unsubscr...@googlegroups.com.
>> 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 rubyonrails-core@googlegroups.com.
> To unsubscribe from this group, send email to
> rubyonrails-core+unsubscr...@googlegroups.com.
> 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 rubyonrails-core@googlegroups.com.
> To unsubscribe from this group, send email to
> rubyonrails-core+unsubscr...@googlegroups.com.
> 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 rubyonrails-core@googlegroups.com.
To unsubscribe from this group, send email to
rubyonrails-core+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/rubyonrails-core?hl=en.
