Blog
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. Unfortunately, it is not easy to set this up for yourself. So this post should help you get started.
This month, Rangle had the pleasure of being the lead sponsor of ReactEurope 2015 in Paris. Having used ReactJS and Flux architectures in about a third of our projects in the last six months, we were very excited about this event… And what a fantastic event it was: being well organized, with an amazing roster of speakers and talks.
As the Angular team is making progress towards a “beta” version of Angular 2, it’s time to think seriously about your transition plan. At Rangle.io we have been looking into this topic for a few months now and would like to start sharing what we’ve come up with.
Fill in the missing line of the following code that implements a function returning the next Fibonacci number every time it's called.
The function getCount() defined below is supposed to return the next number every time it's called, starting with 1. (So, the first call would return 1, the next call would return 2, the next would return 3, and so on.)
Please post the answer on JSFiddle or similar service, and then post a link to your answer here. You can also post comments below or email Rangle.io's CTO, Yuri@rangle.io, if you wish to share further ideas.
Rangle.io has a unique learning culture. We are focused on a very specific technology (modern JavaScript and HTML5 applications) and a very specific process (Lean UX design with agile continuous delivery) and we've applied these practices to over 2 dozen projects. That has led to certain truths emerging over and over. Truths I'd like to present here, alongside some suggested solutions.
I have been a fan of JavaScript for a number of years now. It's a dynamic and flexible language which gives it a great deal of power. However, unlike compiled languages it is easy for syntax errors and accidental globals to creep into your code without realizing it until you actually try and run the code.