How We Do QA for Kotlin at JetBrains
summary
Kotlin QA evolves from IDE testing into compiler and multiplatform coverage with a dedicated QA team, deeper CI, feature freezes and quality gates for K2 frontend releases. Tooling includes dashboards, regression retrospectives and EAP campaigns with about four EAP Champions validating real projects. Acceptance relies on scenario-based compile/run suites rather than raw code coverage, and the process claims 30% fewer regressions year over year while hiring JVM backend QA and combining manual exploratory checks with automated pipelines.
AI-written summary · about
chapters (15)
- 0:00Intro
- 1:07QA at JetBrains
- 6:49Process Changes
- 10:03High Level Overview
- 13:21Operating with Developers
- 18:01Working with Users
- 20:44Questions
- 22:18Development background
- 23:14Language code coverage
- 23:53User scenarios
- 24:36Internal checks
- 25:13Security
- 26:03Coverage
- 26:59Manual vs Automated
- 30:15Code First
related talks
46mQA to QE: Scaling Quality with Ownership, Code, and Culture
42mThe state of code coverage for Kotlin
45mWhat Would You Say You Do Here? Reframing Your Role In The QA Field
38mThe state of code coverage for Kotlin
36mWhy a Growing Company Needs a Growing QA Team
36mFrom Sledgehammer to Fine Brush for QA
39mHow To Elevate QA In Your Organization
53mWhat Happens When Everyone is QA? And I Mean Everyone!