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 rubyonra...@googlegroups.com.
To unsubscribe from this group, send email to rubyonrails-co...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en.
Wellllll… make Jasmine optional and I'm a happy camper :)
> On Wed, Aug 31, 2011 at 3:10 PM, Wael Nasreddine
> <wael.na...@gmail.com> wrote:
>> +1 too, jasmine for unit testing and capybara for integration tests
> Wellllll… make Jasmine optional and I'm a happy camper :)
From our experience with all rails features, rspec, test-unit, haml,
erb etc.. I don't think anything would be mandatory, but instead
through generators and we choose whatever we want... Anyway Jasmine is
my preference for unit testing and what i said is mere suggestion :)
When you do that, it would be similar to not adding tests on generators or not providing Coffeescript or SASS support in a default new Rails application.
I doubt Coffeescript would be largely used if not included in Rails by default. I prefer Rspec over Test/Unit but I don't see any problems with Rails shipping the last by default. And there are other test units available too, but Rails chose one anyway... And I agree with that.
The only dedicated book I know of is the book from my friend at Gitorious AS, Christian Johansen:
Did you get my point?
On 31/08/2011, at 23:06, Rodrigo Rosenfeld Rosas <rr.r...@gmail.com> wrote:
While reading the 3.1 release notes in Rails Guides, I've stumbled across this phrase:
// place your code here.
* Rails ships with Ruby test generators (because testing is good)
(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
As Rodrigo said, it doesn't matter which framework is used (although
Jasmine is nice and iterates/improves upon several earlier tools). The
A few relevant links:
around it called Evergreen, which has gained a little traction. You
should check it out for inspiration I think, since it does a lot of
things very differently than most other similar libraries. I think
it's far superior to e.g. the jasmine gem.
It doesn't yet work with the asset pipeline, since I've been holding
off for the official Rails 3.1 release. So asset pipeline support will
be there soon.
I'm not really campaigning for this to be included in Rails, honestly
I think I prefer it as a separate library, but if you do go down that
route, at least check out the concepts around which Evergreen is
built. I think it has a much better out-of-the-box experience than
pretty much anything else out there.
Sent from my iPhone
+1 to TDD for js, and +1 to Jasmine - I've been test driving js for a
few years now and Jasmine is a nice tool, probably the best I've used.
It's high time folks were encouraged to write real unit tests for js
rather than use Selenium/Sahi/etc.