In this four-part series, the Angular Show breaks down testing in Angular. Do you test? Should you have automated tests? And if you do test, what types of tests should you implement? Should you unit test? Should you have end-to-end tests? What about integration tests? This series tackles all of these questions and more.In part one, panelists Aaron Frost and Jennifer Wadella invite Joe Eames, CEO of Thinkster.io and Pluralsight author, along with Shai Reznik, founder and author of testangular.com, to share their knowledge and love of unit testing in Angular.While you are most likely performing manual testing, you may not be leveraging automated testing. Automated testing enables us to prevent regressions, increasing the quality of our applications. While many of us may not be leveraging automated testing, it can be extremely valuable when moving fast, when we have multiple developers on a team or in the code base, and perhaps even multiple teams in an organization that is sharing the same code and repository. The end result is confidence. Having a high level of confidence in shipping quality software provides significant value. Of course, implementing an automated testing strategy comes at a cost. Weighing the benefits with the cost is critical and should not be missed in your organization or team.Don't forget to subscribe so you can be notified when Testing Series Part 2 on using Jest for unit testing in Angular is available for download!