Heuristics and hunches in exploratory testing
summary
Argues that exploratory testing depends on concrete heuristics and teaches pimple heuristic, micro‑heuristics like “if-heavy” and “yellow state” exploration, and practices such as narrating tests, pairing, and mind‑maps. Demonstrates finding real bugs — a command‑line tool regression, an IKEA Kitchen Planner oddity, and a LastPass deletion/login inconsistency — and uses concrete techniques (Eclipse, breakpoints, print statements, adding waits) and an awareness test that counts 13 passes to show blindspots.
AI-written summary · about
chapters (22)
- 0:00Intro
- 0:30Alexs introduction
- 3:07What is exploratory testing
- 4:51What exploratory testing isnt
- 6:40Why we need exploratory testing
- 9:27Flow chart
- 12:22Exploratory testing
- 13:37Best practices
- 14:56Why did you do that
- 17:12Heuristics and biases
- 18:39Heuristics in testing
- 20:36The pimple heuristic
- 23:08If
- 24:06Yellow is interesting
- 25:57User feedback
- 27:46Naming
- 29:53Undo and redo
- 31:06Deleting things
- 32:57Test op see
- 35:21Test narration
- 36:56Homework
- 38:46Questions
related talks
45mBuilding Tools to Free up Exploratory Testers
24mExploratory: Testing Humanely, Checking Robotically
42mExploratory Testing Basics, Experiences and Future
43mRegression Obsession
44mEnhancing your Testing Skills with "Mindset Tools"
31mExploratory Testing on Computer Interfaces (APIs)
01h 07mSufficiently Advanced Testing
25mHeuristics to help you design, build, and choose test tools