Building and Testing

The previous chapter served as an introduction to AngularJS and covered nuts
and bolts of the framework project itself, people behind it, and basic usage scenarios.
Now, we are well primed to build a complete, more elaborate web application.
The rest of this book is constructed around a sample application that presents
how to use AngularJS in real-life projects.

In the following chapters, we are going to build a simplified project management
tool supporting SCRUM agile software development methodology. This sample
application will help us to demonstrate AngularJS APIs and idioms as well as cover
typical scenarios, such as communicating with a back-end, organizing navigation,
security, internationalization, and so on. This chapter introduces the sample
application, its problem domain and the technical stack used.

Each project starts with some initial decisions regarding files organization strategy,
a build system, and basic workflows employed. Our sample application is no
different and we are going to discuss build system and project-layout related
topics in this chapter.

Automated testing is a solid engineering practice that is promoted by AngularJS
and the whole ecosystem around it. We strongly believe that automated testing
is mandatory for any but the most trivial projects. This is why the last part of this
chapter is fully devoted to testing: different types of it, mechanics and workflows,
best practices, and tooling.

In this chapter, we are going to learn more about:

• The sample application used in this book, its problem domain, and the
  technical stack used.


• The recommended build system for the AngularJS web applications as
  well as associated tools and workflows.