Intersection of Automation and Exploratory Testing
summary
Claims that exploratory testing drives what to automate and that automation is an invitation to explore; demonstrates using approval tests against a Java Gilded Rose 60-line legacy to generate 60 test cases in minutes and surface odd inputs, shorthand rules and limits. Shows running tests at the API level, checking code coverage, using diffs, keeping disposable automation as documentation, and feeding results into the CI/CD pipeline so failures become prompts for focused investigation.
AI-written summary · about
chapters (10)
- 0:00Start
- 2:56Product is my external imagination
- 12:52What Did You Just Demo? A Demonstration of Test Automation!
- 13:22Exploratory Unit Testing of Legacy Code
- 14:01Combining My ideas of the world, Specification and Code Coverage while Testing
- 14:47Shallow vs. Deep Testing Difference in the Learning
- 18:54Existing automation allows for exploration reach
- 19:27Creating automation forces exploration of details
- 19:50Failing automation is invitation to explore
- 21:00Value of the software we create links to quality of our thinking
related talks
01h 01mIntersection of Automation and Exploratory Testing- 01h 01mIntersection of Automation and Exploratory Testing
31mExploratory Testing on Computer Interfaces (APIs)
24mExploratory: Testing Humanely, Checking Robotically
42mOpening Keynote: Blunders in Test Automation
51mRedefining test automation
24mA Comedy of Errors
49mDoes software testing need to be this way?