What you'll learn

As a codebase grows and its test suite covers even more test cases, an important question arises: How do you know your tests are covering every case? Even when practicing test-driven development, some program branches inevitably become omitted from your test suites, a once-effective testing strategy now fails to capture every case, and team churn causes a loss of context on why certain tests were written the way they were. In this session, Sean Olszewski will explain what mutation testing is, how to use it, how not to use it, and what tooling exists to help you practice automated mutation testing.