Most of the time, testing AngularJS applications means testing JavaScript. We test services and we test controllers. But what about directives? What about components? How do we test compiled and injected AngularJS code?

A couple of days ago I finished my capstone project for the Full Stack Web Development specialization on Coursera. It marks the end of the 6-course specialization about Bootstrap CSS, AngularJS and NodeJS.

During the last 6 months I did the Full Stack Web Development course on Coursera. Since I’m currently about to finish the course by implementing my final capstone project (https://github.com/tuhrig/mebo), I wanted to share my thoughts about the course and its pros and cons.

When you come from a Java background like I do and you take a look at JavaScript, the sheer mass of tools is overwhelming. The ecosystem is evolving very fast with new tools coming up every couple of months. Below, I tried to give a comparison between Java build tools and their equivalent in the JavaScript world.

Whenever you write an AngularJS application, you will use modules. Modules divide your application into small logical units. Some units might depend on others, while some might be totally independent.

AngularJS provides three different ways to create a service:

Program to an interface, not an implementation.

Whenever you build software, you want to create reusable and independent components. In the world of user interfaces, those components are often called widgets. Here’s an example how we can achieve this with AngularJS.

Every backend application has a boot process. Services must be instantiated, connections must be established and configurations must be loaded before the application is ready. How can we achieve something similar for an AngularJS application?

Last week I attended an AngularJS Intensive Workshop by Robin Böhm from Symetics GmbH. Symetics is the company behind www.angularjs.de and provides consulting and training all around JavaScript, AngularJS (1/2) and TypeScript.