preface

Back in 2013, I was working on a content management system that used AngularJS heavily, and the expectation was that we have 80% unit-test coverage. My team struggled . . . a lot. You couldn’t find many materials on testing at the time. It was easy to find a blog post here and there, but it was hard to find something that guided you through everything you needed to know to be successful writing tests in a complete package.

I kept thinking to myself, someone needs to write a book on this. I knew it would be challenging to cover all of the potential use cases, but someone could at least give enough foundational knowledge to show people where to start. Plus, with the upcoming rewrite to Angular 2, there would be a need for quality content regarding testing. The idea for Testing Angular Applications was born.

One day in 2015, Manning Publications contacted me to review a proposal for another Angular book. I agreed, and they sent me a questionnaire to fill out. I was ecstatic to see a question at the end of the questionnaire asking if I had an idea for a book. Of course I did! This was my chance to pitch my book, and I was thrilled at the opportunity. Shortly after I pitched it, Manning gave me a contract to sign that marked the book’s official beginning. Along the way, I was lucky enough to add three wonderful authors who helped bring tremendous value to the effort.