Testing Strategy - New Model, Better Outcomes
summary
Compares concrete testing models (debugger-driven, testing pyramid, cupcake anti‑pattern) and claims teams often accumulate brittle suites — one case creates thousands of BDD Cucumber tests that break on a single change and get forked out of the pipeline. Recommends start small: run one automated end‑to‑end smoke test in CI (cron/Jenkins/Travis) to prove value, use Wordle on issue titles to find churn hotspots, add fast developer specs (Detroit) and mock‑driven design tests (London), and evolve toward contract testing and canary releases for microservices.
AI-written summary · about
chapters (5)
- 0:00Start
- 8:15Δ The Testing Pyramid
- 34:17% Code Coverage (Through Tests)
- 37:29O Exploratory Testing
- 37:54FedEx James A. Whittaker
related talks
50mTesting Strategy: New Model, Better Outcome
28mYour Testing Strategy is broken - lets fix it!
01h 05mMicrotesting
42mIntroducing the benefits of the testing diamond
57mAdvanced Testing Techniques: Tips from the trenches
57mOptimizing Your Testing Team
37mUnderstanding the successes and the pain points of different testing strategies
09m"Effective ways of using BDD concept for Testing"