Shift Left or Squish Right - Testing in a Shifting World
summary
Argues that shifting tests left often collapses testing into automated output checks and leaves deep experiential testing squeezed into production, demonstrates the concrete difference between checking vs testing, and recommends devops fixes that actually change builds, logging and testability so exploration can happen in parallel. Shows automation tools used for fast, repeatable checks, explains why they miss emergent, interaction bugs, and cites a real Rogers one‑day outage to show the cost when deep testing never happens.
AI-written summary · about
chapters (4)
- 0:00Start
- 17:02For testers, testing is storytelling. A story about the status of the PRODUCT... about what it does, how it failed, and how it might fail..
- 18:38What does the business want?
- 24:56Shallow testing? That sounds insulting!
related talks
40mEmbracing Shift-Left Testing
01h 28mShift-Left Testing
20mShift-left testing : Building reliable Data Pipelines
37mDon’t Sh*t-Left: How to Actually Shift-Left
47mMaximizing Outcome: Approaching Product Development with Both Shift-Left and Shift-Right Practices
47mHow Testing is Evolving in DevOps
16mShift Left, Not Off a Cliff: Why Your Testing Strategy Is Breaking Developers
55mShifting Out: A Crucial Dimension To Left And Right