In the world full of bugs explore like Bear Grylls

on YouTube ↗24m

" summary

Claims that exploratory testing depends on switching from automatic to focused attention and that a hard limit is about 90 minutes per session, shows an interactive 20 questions exercise that succeeds in under five questions, and recommends preparing with a notebook or using TestRail to record observations. Emphasizes mission-driven solo sessions more than large teams, warns that routine workflows hide bugs, and demonstrates the method by getting quick, verifiable results.

AI-written summary · about

" chapters (6)

1. 0:00Start
2. 9:29The Difference between Exploratory Testing and a Scenario Based Testing
3. 10:00Think like Sherlock Holmes
4. 18:29What Level of Domain Knowledge Is Required for an Expert or a Tester When Testing an Application
5. 21:12Do You Believe in Cheat Sheets or for Export a Testing Do They Help or Do They Kill Creativity
6. 22:36Exploratory Testing Is Not Needed

" related talks

• 42mExploratory Testing Basics, Experiences and FutureKari Kakkonen · TestCon Vilnius 2017
• 01h 09mThe Art and Science of QuestioningJessica Ingrassellino · CAST 2015
• 43mRegression ObsessionMichael Bolton · QA Fest 2018
• 52mTest Like a CatLanette Creamer · Agile Testing Days 2018
• 42mTest Flow: Improve Yourself with Mental TrainingArd Kramer · TestCon Vilnius 2016
• 44mHeuristics and hunches in exploratory testingAlex Schladebeck · Craft Conference 2019
• 36mHow to defuse a bomb Wait, I mean a bugMichele Campbell · UtahJS Conf 2017
• 37mTesting: The compass for creative explorationAdam Matlacz · 4Developers 2020