Understanding the successes and the pain points of different testing strategies
summary
Interviews of engineers (30–60 minutes each) surface concrete tradeoffs: unit tests run fast and locally but become brittle and impede refactors; integration/end‑to‑end tests give higher confidence but break often, need expensive setup and suffer third‑party drift; teams adopt testcontainers (spinning Docker Postgres) and Pact‑style contract tests to run integration‑like checks locally; code coverage often inflates confidence — 100% coverage can lie; CI/CD automates checks but feels like magic until documented; some teams delete flaky tests outright and recover velocity.
AI-written summary · about
chapters (10)
- 0:00Introduction and talk overview
- 1:51Methodology and interview process
- 3:16Unit testing successes and pain points
- 7:05Integration and end-to-end testing
- 12:21Mock and contract testing evolution
- 18:20Code coverage controversies
- 22:53CI/CD workflows and challenges
- 26:00Observations on testing culture
- 32:20Conclusions and final thoughts
- 33:05Q&A session
related talks
42mIntroducing the benefits of the testing diamond
57mAdvanced Testing Techniques: Tips from the trenches
58mTesting Strategy - New Model, Better Outcomes
44mStrategy for Acing Continuous Testing in DevOps
46mTesting the untestable - patterns and use cases analysis
16mStrategy for Acing Continuous Testing
40mIntegration Testing from the Trenches - Rebooted
48mTesting is Confidence - A Developer's Perspective