The development of Angular 2 is on its way with much talk, hype, and fanfare. Surprisingly, there is not much being said about unit testing. As a responsible developer, you have undoubtedly already written a giant unit test suite to achieve ‘near perfect’ code coverage, and I'm here to let you know, there is no need to throw that all away! While Angular 2 is currently in ‘developer preview’, implying that nothing serious should be built with it currently, the Angular Team has already created a giant wealth of unit tests and a custom testing setup: (https://github.com/angular/angular/tree/master/modules/angular2/test). Unfortunately, it is not easy to set this up for yourself. So this post should help you get started.
link to full post here
If you ask 10 people to define Agile development and you will receive 11 definitions emphasizing different aspects of the process. I got to hear a talk (Presented by Anthony Boobier (Nomad8)) to clear up the confusion of this buzzwords and shed light onto the fundamentals of Agile software development. We looked into what problems Agile is trying to solve and dive deep into the reasons why it works. We undertook a brief journey into the history of software development, explore the principles and values behind Agile and then later focused on how to manage our work in an Agile fashion using its most prevalent flavour, Scrum. Scrum is a development framework in which cross-functional teams develop products or projects in an iterative, incremental manner. It structures development in cycles of work called Sprints. These iterations are no more than four weeks each (the most common is two weeks), and take place one after the other without pause. The Sprints are timeboxed – they en...
Comments
Post a Comment