Intersection of Automation and Exploratory Testing
summary
Exploratory testing drives decisions about what to automate by uncovering real surprises: a demo on gilded rose uses combination approvals to generate and visually inspect inputs, producing about 11,236 combinations and breaking a developer’s environment assumptions in roughly two hours. Teams pair exploratory sessions with coverage reports and disposable automation, expose business-model illusions (2,261 fixed bugs reported in 2.5 years), and find issues that full automation missed in a remotely managed Windows Firewall project. Continuous learning, not a tool argument, decides where effort goes.
AI-written summary · about
chapters (10)
- 0:00Start
- 4:00Product is my external imagination
- 5:58Testers don't break the code, they break your illusions about the code
- 21:11Exploratory Unit Testing of Legacy Code
- 21:36Combining My ideas of the world, Specification and Code Coverage while Testing
- 25:36Leaving a job after 4 years
- 29:48Opportunity Cost
- 35:08Creating automation forces exploration of details
- 35:40Failing automation is invitation to explore
- 41:41Testing Programming Learning
related talks
23mIntersection of Automation and Exploratory Testing
01h 01mIntersection of Automation and Exploratory Testing
24mExploratory: Testing Humanely, Checking Robotically
42mExploratory Testing Basics, Experiences and Future
31mExploratory Testing on Computer Interfaces (APIs)
42mOpening Keynote: Blunders in Test Automation
49mDoes software testing need to be this way?
03mNo more Fooling around -- Skills & Dynamics of Exploratory Testing