Managing App Complexity
summary
Nihongo grows from 25,000 → 100,000 LOC and shifts from three screens to a 30‑way configuration space when adding device, language and display dimensions, so verification becomes the bottleneck. The strategy uses Jenkins CI with a device/OS/light‑dark/language/dynamic type matrix, UI tests ≈90% of the suite, and focused unit tests for text parsing, deck serialization and the conjugator (no system mocking). Screenshot tests catch an iPad sidebar layout regression and accessibility audits run in CI.
AI-written summary · about
chapters (8)
- 0:00Introduction and background
- 4:04Defining app complexity
- 9:28The verification challenge
- 12:46Approaches to quality
- 14:28Unit vs. UI testing
- 17:35Automating UI tests
- 20:37Testing philosophy
- 24:51Advanced testing and wrap-up
related talks
52mLayers of testing in iOS applications
46mModernizing legacy through thousands of contextual tools … per system
18mReinventing App Testing with Agentic Apps
30mOptimizing for Developer Delight
44mEfficient testing UI Android apps by example
35mScalable Testing Strategies
13mDeveloping with AI: Balancing Speed and Code Quality
39mMobile Developer Productivity Panel