Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Unit Testing Best Practices in AngularJS

andyshora.com

Post reply on HN
Print view View original

1–10 of 17 posts

Re: Unit Testing Best Practices in AngularJS

#3

Post by tegeek »

Client side testable code is one of the pinnacle of AngularJS.

Reuseable declarative UI's through Directives, reuseable business logic throug Services and view models (controllers) having only knowledge of views is a really good for maintainablity of a complex javascript app. AngualrJS can beat any framework out there (Backbone, Ember, etc.) when it comes to having testable & manageable code.

If your product is going to be complex, AngularJS is a no-brainer deal.

Re: Unit Testing Best Practices in AngularJS

#5

Post by mgr86 »

tegeek wrote: post #3

Client side testable code is one of the pinnacle of AngularJS. Reuseable declarative UI's through Directives, reuseable business logic throug Services and view models (controllers) having only knowledge of views is a really good for maintainablity of a complex javascript app. AngualrJS can beat any framework out there (Backbone, Ember, etc.) when it comes to having testable & manageable code. If your product is going…

I'm curious, is there a strong reason to chose AngularJS over other non JS frameworks. Say, Rails, Django, or one of the many other alternatives?

I realize this thread has me walking into the AngularJS den, but it is something i've been passively curious about.

Re: Unit Testing Best Practices in AngularJS

#6

Post by WalterSear »

mgr86 wrote: post #5
tegeek wrote: post #3

Client side testable code is one of the pinnacle of AngularJS. Reuseable declarative UI's through Directives, reuseable business logic throug Services and view models (controllers) having only knowledge of views is a really good for maintainablity of a complex javascript app. AngualrJS can beat any framework out there (Backbone, Ember, etc.) when it comes to having testable & manageable code. If your product is going…

I'm curious, is there a strong reason to chose AngularJS over other non JS frameworks. Say, Rails, Django, or one of the many other alternatives? I realize this thread has me walking into the AngularJS den, but it is something i've been passively curious about.

It's a bit of an Apples-to-Oranges comparison to compare a client-side framework to server-side ones.

Re: Unit Testing Best Practices in AngularJS

#7

Post by camus2 »

mgr86 wrote: post #5
tegeek wrote: post #3

Client side testable code is one of the pinnacle of AngularJS. Reuseable declarative UI's through Directives, reuseable business logic throug Services and view models (controllers) having only knowledge of views is a really good for maintainablity of a complex javascript app. AngualrJS can beat any framework out there (Backbone, Ember, etc.) when it comes to having testable & manageable code. If your product is going…

I'm curious, is there a strong reason to chose AngularJS over other non JS frameworks. Say, Rails, Django, or one of the many other alternatives? I realize this thread has me walking into the AngularJS den, but it is something i've been passively curious about.

AngularJS is a javascript front-end framework, it has little to do with the server, you still need Rails,Django,Spring or whatever to manage your server-side application.

Re: Unit Testing Best Practices in AngularJS

#8

Post by joshuacc »

mgr86 wrote: post #5
tegeek wrote: post #3

Client side testable code is one of the pinnacle of AngularJS. Reuseable declarative UI's through Directives, reuseable business logic throug Services and view models (controllers) having only knowledge of views is a really good for maintainablity of a complex javascript app. AngualrJS can beat any framework out there (Backbone, Ember, etc.) when it comes to having testable & manageable code. If your product is going…

I'm curious, is there a strong reason to chose AngularJS over other non JS frameworks. Say, Rails, Django, or one of the many other alternatives? I realize this thread has me walking into the AngularJS den, but it is something i've been passively curious about.

Generally speaking, you'd use Angular with a backend framework.

Angular and other front-end frameworks are great for responding to user interactions extremely quickly, because often you don't have to go back to the server. And in addition when it does need to interact with the server, it is often faster to respond because it doesn't need to fetch anything but JSON data.

But that data needs to come from somewhere. And that's where Rails/Django/Play/Symphony/whatever are used.

Re: Unit Testing Best Practices in AngularJS

#9

Post by michaldudek »

mgr86 wrote: post #5
tegeek wrote: post #3

Client side testable code is one of the pinnacle of AngularJS. Reuseable declarative UI's through Directives, reuseable business logic throug Services and view models (controllers) having only knowledge of views is a really good for maintainablity of a complex javascript app. AngualrJS can beat any framework out there (Backbone, Ember, etc.) when it comes to having testable & manageable code. If your product is going…

I'm curious, is there a strong reason to chose AngularJS over other non JS frameworks. Say, Rails, Django, or one of the many other alternatives? I realize this thread has me walking into the AngularJS den, but it is something i've been passively curious about.

It's not "this or that". AngularJS is a complementary framework for client side instead of server side.

That said, AngularJS can offload a lot of server side work. Mainly rendering views and the overall presentation layer. You can basically ditch your server side templating system and make your Rails, Django, PHP or node.js a simple REST API endpoint (with some additional auth system based on cookies or smth).

Post reply on HN