Does it work? Did you test it?
summary
Argues automation alone fails because exhaustive permutations are impossible—915 million permutations illustrates scale—and recommends building state diagrams into runnable test plans that list initial state steps and verifications. Shows concrete checks: repeat runs to catch race conditions, upgrade-path testing (store build → release build), permissions and parental‑control edge cases, hardware/network permutations, and using local JSON mocks and Charles to simulate API instability so tests exercise real-world data transitions and recovery.
AI-written summary · about
chapters (27)
- 0:00Intro
- 3:49Alarm Clock
- 7:39Test Plane
- 10:20Automation
- 11:53What to test
- 13:30Dont test happy path
- 14:14Expect the unexpected
- 14:52Test the upgrade
- 15:21Upgrade from store to release
- 16:19Do it again
- 17:04What if
- 17:33Testing paths
- 18:14Clean launch
- 19:36Testing on real devices
- 20:14Things to consider
- 20:55Case study
- 21:21Camera availability
- 22:37Permissions
- 23:11Your app isnt in a vacuum
- 23:56What data can your app have
- 24:55Data stability
- 28:45Whitebox testing
- 30:06API data
- 30:35Practice
- 31:14Test Plan
- 31:58QA
- 33:28Bugs
related talks
43mCan you Test it
27mWrite Fewer Tests! From Automation to Autogeneration
47mIs Survival of the Fittest Only for the Fastest?
01h 19mYou Can't Test This? Hammertime!
51mAutomating to augment testing
01h 01mIntersection of Automation and Exploratory Testing
39mYou're Testing WHAT?
23mIntersection of Automation and Exploratory Testing