Can you Test it
summary
Claims a small team can test without dedicated QA by building concrete test artifacts: state diagrams that convert to linear test plans, a simple alarm‑clock example that proves the method, and checklists for happy path, negative, upgrade and repeated tests. Notes tool specifics like using Charles proxy to mutate API responses, archiving old builds for upgrade paths, and a combinatorics warning (915 million Lego combinations) to show brute force automation is impossible. Practical steps and failure modes are shown, not just promises.
AI-written summary · about
chapters (32)
- 0:00Intro
- 1:35Testing is Hard!
- 2:07Automation?
- 2:27Permutations and You
- 4:10Alarm Clock
- 4:52State Diagram: NOT SET State
- 5:08State Diagram -- ALARM SET State
- 5:22State Diagram -- ALARM Transition
- 5:33State Diagram: Part 1
- 5:50State Diagram: Completed
- 8:06Test Plan: NOT SET to ALARM SET
- 8:37Test Plan: ALARM SET to NOT SET
- 8:54Test Plan: Full Diagram
- 11:34What Should You Test?
- 12:35Happy Path and what it isnt
- 13:06Negative is Positive
- 13:36Did they really just do that?
- 13:46Upgrade Upgrade Upgrade
- 15:20Get to know your app
- 16:08App Launch
- 16:31App Icon Tapped
- 17:53App Deeplink
- 18:25Hardware States - Fixed
- 19:12Hardware States - Variable
- 19:46Permissions - or lack thereof
- 22:34API Data
- 28:35The Black Box
- 30:45Charles Proxy
- 31:53Tying It All Together...
- 32:30State Diagram vs Test Plan
- 33:06QA Process
- 34:44CRASHES ARE BAD
related talks
35mDoes it work? Did you test it?
45mBuilding Tools to Free up Exploratory Testers
01h 19mYou Can't Test This? Hammertime!
39mYou're Testing WHAT?
58mTesting Strategy - New Model, Better Outcomes
46mHow to Build a Test Automation Tool That Works in Agile
56mNo QA resources? You can still deliver a quality website
01h 05mMicrotesting