Not to start a flame war, but I'm not sure this is a plus. Full unit coverage is nice for confidence, but can be balls and chains when it comes time to make changes.
Ask any of our pre-1.0 users; they'll assure you that the pace of change was breakneck and certainly not hindered by our unit tests.
I can confirm this. Oh boy, can I ever confirm this.
Tom, do you know if anyone has written extensively about tests in Ember? Or is the source still the best go-to?
Re:Migrating from Ember.js to AngularJS
by logical42 on Tuesday February 05, 2013 @01:05AM
(#5169418)
I will vouch for this as well. I have still, very conflicted feelings about the improvements in the router and having to rewrite large portions of the app I was (and am still) working on.
@tomdale thank you for the breakneck speed in development, it amazes me how much the project has evolved in the time I've been using it.
I've been using Angular for months now and although I already knew what dependency injection was, I didn't have to understand the term to use Angular.
> Additionally, Ember is fully unit tested.
Not to start a flame war, but I'm not sure this is a plus. Full unit coverage is nice for confidence, but can be balls and chains when it comes time to make changes. Just as an example, Rails is not fully unit tested by any stretch of the imagination.