The AST CASTcast: Episode 12: Session Based Testing in an Agile Project
summary
Session-based testing adapts exploratory work into sprint cadence by preparing before code lands: create intake notes from user stories, run a survey to gather dependencies, configure devices and backend in a setup session, perform risk-based idea generation in analysis, then execute timed 60–120 minute deep coverage sessions with test IDs, charges and meticulous notes; automation or BDD-style steps appear only where useful; six session report types map to concrete outputs (environment matrix, risk list, test IDs, executed session logs) that show what was built and what actually fails.
AI-written summary · about
chapters (8)
- 0:00Welcome to CAST podcast
- 0:29Guest: Simon Peter Shrivever
- 1:54Simon’s testing career
- 3:20Agile sprints and tester’s role
- 4:26Exploratory testing and automation
- 6:56Session-based testing preparation
- 8:21Deep coverage and risk assessment
- 9:45Why attend Simon’s CAST talk
related talks
20mAutomated Testing
22mOvercoming the obstacles of Exploratory Testing at scale
02mPradeepa Narayanaswamy on CAST 2014
36mContext-driven Agile Tester
02mHilary Weaver on CAST 2014
09m"A few things about Agile Testing"
46mHow to Build a Test Automation Tool That Works in Agile
49mBalancing Release & Sprint Delivery Speed with Thorough Testing