Live Exploratory Testing
summary
Live exploratory testing against a Bookshelf web application shows code runs locally, API specs exist but not in OpenAPI form, and Bruno plus PyCharm and a bulleted note tool capture the session; happy‑path suites run multiple times and pass, but many test files are just API calls with no asserts on responses, fixtures leak state, 404 and 405 behaviors appear, token auth is used yet traffic is not HTTPS, and test repos sit separate from the app repo.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 1:54Exploratory testing buzzwords
- 6:31Live test mission
- 9:42Local product run
- 12:27API endpoints testing
- 17:28Test suite review
- 22:50Test coverage assessment
- 28:11Unhappy path analysis
- 31:46Findings and next steps
- 33:08Further learning resources
related talks
24mLive Exploratory Testing
31mExploratory Testing on Computer Interfaces (APIs)
20mGo Find What We May Have Missed!
40mIt's A Livebook
33mLet's Explore Our APIs
43mValidating Entire User Journeys by Isolating Front Ends using OpenAPI
42mAutomated Tests: You Won't Find It in a Book!
45mBuilding Tools to Free up Exploratory Testers