My take. Use selenium, power it through cucumber.
Only use it when testing AJAX. Avoid in-browser testing wherever possible, otherwise your build times will sky rocket! On 26/11/2009, at 16:41, Daryl Manning <[email protected]> wrote: > Just post Railscamp we're trying to be a lot better about testing > and we've got at least one new app which has a small greek army of > ajax (ajaxes? ajaxi? ajuxes?). > > Was very curious as to what other people down here in Oceania are > using to do their js and ajax testing. So far, Blueridge is looking > good, but curious as to pros and cons from everyone who tests this > stuff regularly. > > thanks ! > Daryl. > PS> So, yes watir, selenium and others are in there as well and just > trying to find something to standardize on in here. Caveats: We've > got a small dev team so it can't have too much of an admin or > learning curve footprint > -- > > You received this message because you are subscribed to the Google > Groups "Ruby or Rails Oceania" 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/rails-oceania?hl=en > . -- You received this message because you are subscribed to the Google Groups "Ruby or Rails Oceania" 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/rails-oceania?hl=en.
