Impact Analysis: How We Speeded Up Unit Tests
summary
Explains how an Android team reduced unit test run time using impact analysis and related tooling in their CI/CD. Describes the tools and techniques applied on the Sberbank Online project, the speed improvements achieved, and the practical pitfalls encountered during implementation.
AI-written summary · about
chapters (15)
- 0:00Introduction
- 2:31Slow builds and solution
- 3:33What is unit testing
- 4:17Impact analysis: essence and benefits
- 5:46Running tests with analysis
- 10:13Sberbank Online project
- 11:40Test approach evolution
- 12:00Impact analysis algorithm
- 14:50Change types and handling
- 21:04Class dependency tree
- 25:42File-to-class mapping
- 29:19Kotlin problem and solution
- 32:11Impact analysis plugin setup
- 37:53Test optimization results
- 39:20Q&A
related talks
01h 00mTest Impact Analysis for Android & JVM
52mTest Impact Analysis. Smarten up your pipeline and reduce t
45mThe Balance Between Speed and Reliability: Reuse vs Re-verify
29mHow to Shorten UI Test Run Times
35mThe Impact of Micro-Optimizations on Large-Scale Apps
25mDevOps for Android supercharged with AI
26mAndroid CI: 2016 edition
34mSetting up Android UI Testing on CI