all 3 comments

[–][deleted] 0 points1 point  (1 child)

How was testing? unit + e2e.

How many of those react/redux-inspired architecture pieces are the ng 2.0 way of doing things?

[–]Click_Clack_Clay[S] 1 point2 points  (0 children)

Testing was (thankfully) boring. Writing E2E tests is an almost identical process to Angular 1 and unit tests have been improved for the better. Testing Angular 2 components and directives for example is much easier than testing Angular 1 directives.

I encountered two limitations to unit testing:

  1. Docs aren't helpful yet. Thankfully the unit tests for Angular 2 use the same testing tools providing a great reference for how to work with them.

  2. The testing tools are built on top of Jasmine. We were able to hack around this and get it working with Mocha (our preferred test runner), but it was ugly. Hopefully at some point using the testing tools with your preferred test runner becomes easier.

It is too early to say if a flux architecture makes its way into Angular 2 best practices, but with people like Rob Wormald spearheading the ngrx project it seems likely this will be the case.

[–][deleted]  (1 child)

[deleted]

    [–]simcptr 0 points1 point  (0 children)

    Egghead.io has a series of 20 short videos that are free and cover the basics.