Access Points for Testing: From Human Opportunities to Digital Techniques
summary
Argues that designing for testability actually lengthens usable testing time by adding concrete access: test modes and remote debugging let teams attach debuggers and flip logging levels at runtime; branch-per-feature deployments give immediate, shared environments; synthetic data and simulated devices replace scarce hardware (real cell-imaging devices refuse to produce edge cases); a digital twin of the drug‑manufacturing supply chain at Astroenica enables scenario runs; example mapping (30 minutes daily) and conversational techniques uncover rules and failures early.
AI-written summary · about
chapters (14)
- 0:00Introduction
- 1:50Access points in testing
- 4:23Designing for testability
- 6:12Human testing processes
- 13:03Visualizing requirements
- 18:17Example mapping
- 21:48Technical feedback loops
- 26:51Logging and observability
- 29:40Hardware-software debugging
- 31:47Access to real users
- 33:31Telemetry for testing
- 35:20Continuous learning
- 36:25Key takeaways
- 38:14Q&A
related talks
57mAdvanced Testing Techniques: Tips from the trenches
24mLeveraging Automated Testing Data to Enhance User Experience
30mBest Practices for Accelerating Continuous Testing
44mHow Testability Supports Your Agility
30mElevating User Experience Through Effective Testing Strategies
39mModel Based Testing Shifting Right into the Real World
01h 05mMicrotesting
32mWhy testing is a developer's problem