Plugin Testing: Performance, UI, and Functional Testing
summary
The IntelliJ Platform’s integration framework is now public and reproducibly runs plugin installs, UI actions and assertions, and performance traces using starter and driver; tests launch real IDEs (from 2024.2+), install the build, drive the UI with Java AWT Robot and a JMX-based driver across two JVMs, and capture screenshots, recordings and CPU/memory snapshots. JetBrains runs about 600 tests daily covering ~100 updates (most pass); internally there are thousands of starter tests and ~200s of UI tests. OS permissions and physical hardware matter for stable performance results.
AI-written summary · about
chapters (8)
- 0:00Plugin testing intro
- 3:58JetBrains smoke testing
- 7:31Plugin testing starter
- 11:11UI testing challenges
- 14:50Reliable UI integration
- 19:50Debugging UI tests
- 21:54Future testing tools
- 23:42Q&A
related talks
06h 30mJetBrains Plugin Developer Conf 2025
42mHow an IntelliJ IDEA Plugin Can Help You in QA Automation
22mTwo years of UI Testing
58mHow We Support New Technologies, Languages, and Frameworks in IntelliJ IDEA
54mHow IntelliJ IDEA Performance Improved: Past, Present, and Future
46mHow we’re improving performance of IntelliJ IDEA Kotlin plugin
51mAre Your Test Slowing You Down?
42mEffective Developer Testing: taking it to the next level