#testedAF: Test All the Things (Not Just Your Units)
summary
Kessel Run claims it cuts initial product launch to ~120 days and shifts teams to weekly deploys by treating testing as continuous validation of assumptions, not just unit checks. Practices include TDD and pairing, CI/CD with Concourse pipelines, security scans (SonarQube, Fortify), exploratory testers on teams, capability stories and challenge days, monitoring-driven development, and tooling like Java tests, Cypress and Puppeteer. At scale 18 product teams run test suites ~33,000+ times since 2017 to keep feedback loops short and risk low.
AI-written summary · about
chapters (20)
- 0:00Intro
- 0:46Test all the things!
- 3:08Devos like a butterfly
- 3:54When you say all the time
- 6:10Pre-build Testing our Assumptions
- 7:02Lean Product Management
- 8:38Lean approach to implementation
- 9:45Extreme Programming (XP)
- 11:11Pyramid or filter?
- 12:06Outcomes
- 14:09Exploratory Testing
- 16:23Real-time PM Acceptance
- 17:11User Acceptance
- 18:45Monitoring Driven Development Shift Left
- 20:48Conway's law
- 21:03Balanced teams in spheres of influence
- 21:53Build systems the same way you build apps
- 22:43Who writes a capability story?
- 23:32How do we build a system of systems?
- 23:58Desired Benefits for
related talks
33mTESTING IN PRODUCTION
42mTesting in a Continuous Delivery World
26mThe Impact of Testing on a DevOps Pipeline
36mHow programmers & testers can be productive
20mThe Road to Continuous Testing
45mTesting the web without testers — success or failure
44mStrategy for Acing Continuous Testing in DevOps
22mTesting in Production