The Test Safety Net: Reviving Unit Tests and CI
Roadmap note — open work items #130, #106, #30, #124, #125, #107, #129
Every refactoring wave needs a net to catch it. The 2026 modernization already refactored all
17 plugin bundles and the core com.p2pframework bundle to Java 17 — but the unit-test
infrastructure that guarded the code in 2013–2015 (Kaneriya's testing thesis, Liu's benchmark
harness) has not run since the build systems changed.
What's open, and why it is worth doing:
- Restore and modernize the unit test infrastructure (#130) and resurrect the existing
unit tests (#106): the old tests encode fifteen years of tribal knowledge — they know
exactly where the edge cases of
DistributedSet, the storage dispatcher and the message dispatcher live. Getting JUnit onto the modern classpath is a weekend task with a multiplier effect on everything else. - Unit tests in the pipeline (#30): once green, wire them into the GitLab CI so every merge request runs them automatically.
- Check regressions for the bundle you touched (#124) and interactive testing right before presentation (#125): establish a small "definition of green" ritual per sprint.
- Test through the OSGi Equinox console (#107): drive a running cluster with console commands — cheap end-to-end checks without GUI clicks.
- Migrate ImageHelper to the current commons-imaging API (#129): one of the last deprecated library dependencies standing between us and a clean build.
The prize: with tests running again, the pace of the 2027 work (Bndtools migration, DDS completions) can double without fear. This is the single highest-leverage open item.