Testing in a complex world
summary
A practical claim: designing testability and operability from the start measurably cuts risk — testability lowers likelihood of failures, operability shortens MTTR and limits impact. Example environment: Glofox runs on AWS with dozens of interconnected services and third‑party APIs like Stripe, so teams assume partial failure and ship small, frequent changes. Metrics cited are Accelerate indicators (lead time, deployment frequency, change failure rate, MTTR) as evidence this approach works.
AI-written summary · about
chapters (4)
- 0:00Who is the smug kid on the right?
- 1:29There are real costs to software failure, financial and human, for both our users and the people building and operating our software systems.
- 1:50We're working in an increasingly complex world where everything is connected, change is continuous and failure can be catastrophic!
- 6:38Cultivate an environment in which an amazing delivery team experience will emerge!
related talks
44mHow Testability Supports Your Agility
15mTestability: when your testing problem isn’t testing
22mLet’s dive into the topic of testability
15mTransforming Testing: The Power of TestOps
39mAccess Points for Testing: From Human Opportunities to Digital Techniques
24mTesting Less, Achieving More: How we mastered The Art of Strategic Testing
06mWhy do we need to test?
24mThe more we test, the worse?