EPIC Experience 2020 Concurrent Session : Test Design for Continuous Delivery

SEE PRICING & PACKAGES

Thursday, April 23, 2020 - 11:00am to 12:15pm

Test Design for Continuous Delivery

Add to calendar

Imagine that within moments of being submitted into the code repository, a new feature automatically releases straight into production. Is this your team’s dream or their nightmare? The answer depends not just on the continuous build pipeline, but on the quality and coverage of the battery of your tests. The difference between shipping a product quickly and shoveling garbage into production quickly lies in what the appropriate battery of tests should be. Automated build architectures don't always lend themselves well to the traditional stages of testing. In this hands-on tutorial, Melissa Benua will introduce key test design principles—applicable to agile organizations both large and small—that allow you to take full advantage of the pipeline's capabilities without introducing unnecessary bottlenecks. Learn how to make highly reliable tests that run fast and preserve just enough information to let testers and developers determine exactly what went wrong and how to reproduce the error locally. Explore ways to reduce overlap while still maintaining adequate test coverage, and learn how to rely on observability to backstop your testing efforts.

Melissa Benua
mParticle

Melissa Benua has worked in nearly every software development role—dev, test, DevOps, and program management—at companies big and small and somewhere in between. She's created and run high-availability, high-quality services for PlayFab, Bing, Cortana, and Xbox One, and now for mParticle's enormous data platform. Melissa discovered her love of massively scaled systems while growing Microsoft's Bing back end, where she honed the art of keeping highly available, complex systems up while undergoing significant code churn. Now an engineering leader with mParticle, she’s passionate about not only maximizing efficiency in her product code and in her developer tools, but also sharing best practices among colleagues and with the DevTestSecOps world at large.