Fighting regressions in Kotlin
summary
Kotlin establishes a regression-prevention pipeline starting Spring 2022 that combines root cause analysis, analytics monitoring and a tracking bot called swagbot plus a dedicated release team and stricter quality gates. The process enforces responding to new regressions within a week, required RCA for major fixes, and surfaced 150 legacy regressions during transition; it delays releases when needed (1.7.20) and drops yearly regressions from 437→318 (≈30%) cutting about 119 regressions a year and stabilizing open critical bugs to single digits.
AI-written summary · about
chapters (6)
- 0:00Introduction to Kotlin QA
- 1:05The importance of stability
- 3:38Defining the regression problem
- 4:26Strategies for improvement
- 7:25Implementation and results
- 9:43Conclusion and outcomes
related talks
48mKotlin 2.0 and beyond
16mHow to get satisfaction from ungrateful work: A journey into updating Kotlin
41mReviewing Kotlin
38mKotlin Language Features in 2.0 and Beyond
32mHow We Do QA for Kotlin at JetBrains
42mKotlin Adoption in the Giant Java Application
23mKotlin
52mKotlin Backend Development 6 Yrs Recap. The Good, the Bad and the Ugly