Most engineering teams treat resilience testing as a post-deployment concern — something to revisit after an incident rather than build in from the start. The result is partial risk detection, lingering business exposure, and the kind of downtime that’s entirely preventable. The question isn’t whether to test for resilience, but where and how to make it systematic across every phase of the Software Development Life Cycle.
Join Uma Mukkara, Head of Harness Resilience Testing and Co-Creator of LitmusChaos, for a practical session on embedding resilience testing into your SDLC. Uma will walk through what it means for a service to be resilient against system failures, high load, and disaster scenarios — and why leaving any of those gaps unaddressed raises your operational risk.
You will learn the following:
- An understanding of chaos testing, load testing and disaster recovery validation
- You’ll leave with a clear framework for where each type of testing belongs and who is responsible for it.
- How AI-powered tooling can help you quantify and mitigate risk before it reaches production.
Umasankar Mukkara
Head of Chaos Engineering
