UI Testing for Fun and Profit
summary
Research documents a path from zero to pragmatic UI testing: Trello currently runs 834 unit tests, adds Xcode UI tests as nightly smoke checks (not CI) because UI tests fail ~20% of runs, and uses Fastlane snapshotting plus Bluepill to parallelize simulators. Recommendations include mocking the network layer to speed tests, disabling animations, using accessibility identifiers, and incrementally adding UI smoke tests and snapshot coverage rather than a risky full MVVM refactor.
AI-written summary · about
chapters (22)
- 0:00Intro
- 0:16UI TESTING For FUN ... and PROFIT?!
- 5:11WHAT ARE WE DOING?
- 5:45ALL THE WAYS WE TEST
- 5:57COMPILER
- 6:08SIMULATOR OR DEVICE
- 6:22UNIT TESTING
- 6:56INTEGRATION TESTING
- 9:17CONTINUOUS INTEGRATION
- 10:04BETA TESTING
- 10:43RELEASE TESTING
- 11:22PRODUCTION TESTING
- 13:25Consolidated code coverage → Seamless integration with build process
- 14:32WATCH
- 14:58SIRI
- 15:46ANIMATIONS
- 15:57ALERTS
- 16:16TRANSLATIONS
- 16:55WHAT DID I LEARN?
- 18:10WHAT ARE OTHER TEAMS DOING?
- 19:24KICKSTARTER
- 21:11WHAT SHOULD TRELLO DO?
