Exploratory Testing - MobTesting, BugBashing, CrowdTesting, Oh, My!
summary
Covers three hands‑on methods: one-device mob testing with rotated driver/navigator/note‑taker roles and ~5‑minute turns producing many fresh perspectives; a 90‑minute bug bash pattern (10/60/20 split) for multiple devices and quick triage; and crowd testing causing a Heroku dyno failure when the public test site is hit hard — the testing playground is built and finds real bugs but collapses under load, and dozens of defects and prize winners emerge.
AI-written summary · about
chapters (35)
- 0:00Intro
- 0:50Interactive Exploratory Testing
- 1:32Overview
- 3:11Seville
- 3:35Bunnings
- 4:46MobTesting
- 13:23CrowdTesting
- 16:03Green Website
- 16:43Good Bugs
- 17:23Search
- 18:13Mob Testing
- 19:18Bugs
- 22:13Wrapping Up
- 23:13What is BugBashing
- 23:53Power of BugBashing
- 25:08Entry Criteria
- 25:48Preparation Meeting
- 26:28Stager
- 26:48Bug Bash
- 27:43Practice Session
- 28:33Crowd Testing
- 29:03Crowd Testing Diversity
- 29:38Crowd Testing Scalability
- 30:38Crowd Testing Communication
- 31:08Crowd Testing Quality
- 31:33Confidentiality
- 31:53Tracking and Managing
- 32:23Motivation
- 33:13CrowdTesting Challenge
- 38:13Prizes
- 38:53Buddings Website
- 40:13Prize
- 41:13Bad HTML
- 41:33Juggling
- 42:23Winner Announcement
related talks
45mBuilding Tools to Free up Exploratory Testers
59mLessons learned from mobile crowdtesting
42mExploratory Testing Basics, Experiences and Future
25mOn The Shoulders Of Testing Giants
59mLessons learned from mobile crowdtesting
45mPanel Discussion | Test Automation Trends
44mHeuristics and hunches in exploratory testing
08mVariations During Testing