I’ve known Jesse Palmer for many years as part of the Angular community, so I was excited when he told me he’d be writing a book specifically focused on testing for Angular projects. I’ve seen firsthand how hard it can be to do a great job at automated testing on some of the world’s biggest applications. As a result, when I started the Angular project, I wanted to make sure everything we did contributed to making testing easier and even a joyful experience.

I was hired at Google primarily for my experience in testing, and my first roles here were in improving test techniques, infrastructure, and adoption of testing for products like Gmail, Google Calendar, and Google Docs.

At Angular’s core, we’ve set the application architecture itself to be testable, with dependency injection, mocks, and API hooks for end-to-end testing. We’ve built tools like Protractor for easy, stable, and fast end-to-end tests. We built Karma for a great developer experience in unit testing. And there’s still more to do!

This book picks up where we on the Angular team left off. It provides guidance on the overall strategy for how to think about testing on your projects to get the best return on your investment. It dives into specifics for testing different aspects of your applications. And it covers what are often regarded as advanced topics, such as setting up continuous integration for your tests and doing screenshot diff testing.

So here’s my big thank you to Jesse, Corinna, Mike, and Craig for writing this book and helping to build a stronger, smarter Angular community.

And thanks to you for being part of the Angular community and taking the time to improve your skills.

Brad Green Engineering Director for Angular at Google