Release & Iterate Faster: Stop Manual Testing
summary
LinkedIn moves from monthly manual regressions to a CI pipeline that targets a commit-to-member window of three hours and a product goal called three by three. The system runs about 6.5k tests per build, parallelizes work with 16 emulators on one CI machine, uses distributed builds and apk splits, auto-reverts failing commits, runs trunk guardian to disable and require fixes for flaky tests, ships to a capped Google Play public beta, and relies on feature flags for safe rollouts.
AI-written summary · about
chapters (30)
- 0:00Introduction
- 0:27Ideal Release Schedule
- 3:06Nobody Was Happy
- 4:30Project Voyager
- 5:43Easy Engineering Answer
- 6:10The Real Goal
- 7:22Three by Three
- 8:05Why 3 Hours
- 9:50Commit Line
- 10:52Static Analysis
- 12:42Building the Code
- 14:32LinkedIn Pipeline
- 15:44Android Gradle 30
- 16:46Unit Tests Layout Tests Scenario Tests
- 18:37How Do We Measure Coverage
- 20:49Speed
- 24:36Reliability
- 26:33Trunk Guardian
- 29:01Distribution
- 29:41Release Automation
- 30:32Beta Distribution
- 32:59Production Release
- 34:19Current Schedule
- 35:47Feature Flag Infrastructure
- 36:25Manual Testing
- 39:18Mindset Shift
- 39:58Balls in the Air
- 43:02Beta Testing
- 43:46Crashes
- 47:24Release every 3 hours
related talks
29mOur Journey to Fully Automated Weekly Releases
27m3x3 Fresh Code Delivered, Three Times a Day
53mTransforming testing methodologies: From manual to robust strategies
38mFrom Development to Production: Tips to Optimise Android App Deployments
32mClimbing the Mountain of CI/CD: A Tester’s Tale
05mRelease management as a catalyst for CI/CD
57mThe Road to Mobile DevOps for Android
26mContinuous Everything in Mobile