No product to test yet? No problem.
summary
Testing starts before a single line of code and focuses on concrete risks: an export button hidden under an ellipsis, exports queued then requiring manual download with no progress indicator, and a merge feature that defines "duplicates" nowhere and allows a single ambiguous resolve action that once merged millions of contacts into one. Reviews center on asking specific questions — start testing before code, show me the data — checking data integrity, recovery paths (undo and recovery), realistic complex use cases, consistency and clear user feedback.
AI-written summary · about
chapters (7)
- 0:00Introduction to testing design
- 1:07Why testers should review designs
- 6:07Dogfooding reveals hidden flaws
- 7:54Example one data export failure
- 13:21Example two contact merging issue
- 19:56How to review product designs
- 25:38Key takeaways and conclusion
related talks
30mDeveloping Product Review Practices (That Work)
39mYou're Testing WHAT?
20mPanel Discussion on Testing
23mChaos Survival Guide: How to Start Testing if There is Nothing to Help You
45mBuilding Tools to Free up Exploratory Testers
09m"How to be a customer obsessed tester?"
01h 34mShift left in testing: Find bugs before they’re implemented
41mSheekha Singh: You cannot TEST everything