Shift left in testing: Find bugs before they’re implemented
summary
Development teams run a pre-story feature kickoff using a physical deck of cards to interrogate assumptions (six question cards), examine perspectives (physical, logical, activity) and pick quality attribute cards (security, performance, analytics). A concrete example: adding “create up to three users and assign seats” surfaces unanswered questions about batching vs sequential API calls, transactional failure modes, email delivery and SVG upload security. Engineers own testing, run QA kickoffs, QA demos and bleed exploratory sessions, and repeat kickoffs when answers change, preventing many late, costly bugs.
AI-written summary · about
chapters (14)
- 0:00Intro
- 0:45Agenda
- 1:28Perspective
- 3:48QA kickoff
- 8:50Exploratory testing
- 9:37Feature kickoff
- 12:08Cards in the deck
- 15:02Interrogation
- 16:37Integration
- 19:30Integration Example
- 23:33Integration Exercise
- 36:55Questions
- 43:35What will we do
- 46:55Second exercise
related talks
33mAgile Software Testing
24mImproving Development Quality and Speed with Agile Testing
28mRisk Based Testing in Agile Teams
59mBabble & Dabble: Creating Bonds Across Disciplines
19mHow can we improve quality on a project?
14mCommunication is Key: Lessons Learned from Testing in Healthcare Technology
16mShift Left, Not Off a Cliff: Why Your Testing Strategy Is Breaking Developers
49mTest Strategy in a SCRUM Environment