"A Case for an Edge Case"
summary
Three concrete failures and their costs: an iPhone SOS froze UI that triggers emergency alerts and causes two to four hours of lost family time; a Lufthansa self bag drop mis-tagged luggage that leaves checked bags in Frankfurt, forces a missed connection and $2,000+ in emergency rebooking; and a cross-account Alexa/Kindle geography mixup that removes expected localized features. Recommendations are specific: read production logs, quantify user risk, do domain and exploratory testing, use heuristics like CRAP and LEAP, and communicate measured risk early and often.
AI-written summary · about
related talks
32mReal Life is not an Edge Case
26mThe software bug all stars - and what we can learn from them
23mMobile App Crashes in Production: Lessons Learned from a Tester’s Viewpoint
24mHow to solve intermittent issues, aka Random Failures
51mThe Chips and Pickle Story: What's Really Behind Infamous, Historic UI Failures?
15mWhy I Prefer Good Testing Over Excellent Testing
50mThe Crisps and Pickle Story: What's Really Behind Infamous, Historic UI Failures?
25mRethinking testing and risk within complex systems – the Swiss Cheese Model