One of the hallmarks of DevOps is making it possible to quickly and safely deploy new functionality to production. Doing so safely is dependent on a protective suite of automated tests that can check for any regressions in the intended functionality.

But who is looking out for the health and safety of those automated tests? Sure, they did their job when they were first written, but they need to keep doing that job as long as the application is in production. That should be years, if not decades. Those tests need to continue to provide safety even as the functionality shifts over time and team members who wrote them leave and are replaced.

Join George Dinwiddie as we explore some ways to keep automated tests healthy.