Go Find What We May Have Missed!
summary
Exploratory testing frames the assignment: React frontend plus real and fake backends, so take control of API responses and see what breaks. Runs the app against OpenWeatherMap API and a mock server with stubs, discovers UI typo ("sunshine" vs "sunrise"), timezone assumptions, city lookup returning the wrong city for a postal code, tolerant typo handling, Kelvin-to-Celsius conversion bug, and missing icons. Argues for combining artifact automation with performance-style exploration and testing across architecture layers.
AI-written summary · about
chapters (6)
- 0:00Introduction
- 2:37Two kinds of testing
- 5:05Building testing teams
- 7:12Hands-on testing
- 17:04Testing beyond app
- 19:55Summary
related talks
36mFake It While You Make It
38mLive Exploratory Testing
31mThe power of mocking APIs
42mFree Your Frontend Client from Backend Cage
27mFantastic Bugs And Where To Find Them by Iris Schaffer (Eng) | JSConfAM19
42mWait, I have to test the front end too?
31mExploratory Testing on Computer Interfaces (APIs)
45mBuilding Tools to Free up Exploratory Testers
