Imagine: as soon as any developed functionality is submitted into the code repository, it is automatically subjected to the appropriate battery of tests and then released straight into the wild. Setting up the pipeline to do just that is becoming more and more common, but most organizations hit the same stumbling block: just what IS the appropriate battery of tests? Automated build pipelines don’t always lend themselves well to the traditional stages of testing. In this hands-on tutorial, Melissa will introduce testers to the key principles of test design that apply to organizations big and small to allow them to take full advantage of the pipeline’s capabilities without introducing unnecessary bottlenecks. Testers will learn how to make highly reliable tests that run fast and preserve just enough information to let the team determine exactly what went wrong and how to reproduce the error locally. They will also explore how to reduce overlap while still maintaining adequate test coverage, about what test areas might be most beneficial to combine into a single suite, and what areas might benefit most from being broken out altogether.