Two years of UI Testing
summary
Subito reports concrete results: UI tests replace manual checks, enabling releases to move from monthly to biweekly and one person handling deployment. The codebase runs 300+ UI tests that originally took ~4 hours per device and after their dispatcher and parallelization cut to ~15 minutes. They open-source SBT itis tunnel to inject network, defaults and file state into tests, and SBT whitus browser to visualize and merge results; one-line UI tests cover roughly six lines of app code and monkey tests reproduce a rare SDK crash.
AI-written summary · about
chapters (11)
- 0:00Introduction and background
- 1:16Why we adopted UI testing
- 3:07Six reasons to use UI testing
- 7:40Main limitations of UI testing
- 9:54Overcoming UI testing limitations
- 12:00Analyzing failing tests efficiently
- 13:26SBTUITestBrowser tool
- 15:16Speeding up slow UI tests
- 16:41Parallel test execution
- 20:11Comparison with Xcode 10
- 21:12Conclusion and call to action
related talks
34miOS Testing on Scale
23mUI Testing for Fun and Profit
45mTesting the web without testers — success or failure
51mUI tests are dead, long live UI tests!
57mInverting Test Pyramid - A First Hand Experience Report
43mUI testing is so easy - said no developer ever
38mScaling Automated Testing & Architecture from Startup to Enterprise
56mThe End Game