Shaking Sticks and Testing OpenJDK Implementations
summary
AdoptOpenJDK/OpenJ9 binaries undergo thousands of checks across functional, regression, system, load, application, performance and JCK suites run on multiple Jenkins servers and a small four‑to‑five person team. A thin wrapper called testkitgen standardizes runs so callers use targets like make functional or make perf. Performance work uses JMH and bumble bench microbenchmarks; results feed a Test Results Summary service and MongoDB for historical triage. Code coverage is tracked (baseline ~71%) and change‑based testing reduces overhead.
AI-written summary · about
chapters (20)
- 0:00Start
- 0:23Who We Are
- 1:54The Scope
- 4:30Innovate and Collaborate
- 5:13Granularity
- 6:11TestKitGen
- 7:37Github repos
- 7:50System Tests
- 9:25Functional/Regression Tests
- 11:23Perf Tests
- 16:22JCK Tests
- 17:37Integrate New Tests
- 19:46Nightly, Weekly, and Release Tests
- 20:33Determining Quality
- 23:58Example of codecov
- 25:47Tests Results: TRSS & Triage
- 27:35Nuances and Lessons Learned
- 29:11Approach to QA of JDK binaries
- 30:15Future Forward Plans
- 31:14Conclusion
related talks
47mAdoptOpenJDK - What is that actually?
44mWelcome to The Jungle - A Safari Through The JVM Landscape
50mWelcome to the Jungle - A safari through the JVM landscape
38mWelcome to the Jungle - A safari through the JVM landscape
47mJava's Hidden Gems: Tools and Libraries
54mJava's Hidden Gems
51mWelcome to the Jungle - A safari through the JVM landscape
49mJava's Hidden Gems: Tools and Libraries