Live Exploratory Testing
summary
Live, practical demo of an actual Bookshelf web app with code, OpenAPI/Swagger specs, and runnable front end; notes taken in WorkFlowy and tests inspected in PyCharm. Finds: empty-book records accepted because there are no validation rules, accessibility contrast is poor, API docs omit security, and many Python tests are TODO/pass or commented out so they pass but do not give release confidence. Shows decision heuristics, oracles, and a debrief.
AI-written summary · about
chapters (12)
- 0:00Live exploratory testing intro
- 1:51What exploratory testing means
- 2:34Oracles and charters
- 4:42Team request and setup
- 6:11Exploring bookshelf frontend
- 8:39Investigating low-code model
- 10:24Noticing curiosities and findings
- 12:33API specs and security
- 14:05Automated tests analysis
- 16:35Confidence for release
- 17:38Summary and next steps
- 20:50Q&A
related talks
38mLive Exploratory Testing
40mIt's A Livebook
31mExploratory Testing on Computer Interfaces (APIs)
20mGo Find What We May Have Missed!
45mBuilding Tools to Free up Exploratory Testers
59mKeynote: Testing Modern Web Apps Like a Champion
08mExample-driven development: bridging tests and documentation
42mAutomated Tests: You Won't Find It in a Book!