Purushottam Sinha created FLINK-40063: -----------------------------------------
Summary: Tests: migrate JUnit 5 (Jupiter) to JUnit 6
Key: FLINK-40063
URL: https://issues.apache.org/jira/browse/FLINK-40063
Project: Flink
Issue Type: Technical Debt
Components: Build System, Tests
Reporter: Purushottam Sinha
Problem
Placeholder to track upgrading the test stack from JUnit 5 to JUnit 6. JUnit 6
keeps the same Jupiter programming model (org.junit.jupiter.api.*), so this is
a junit-bom version bump plus fixing removed deprecated APIs — not a rewrite.
It cannot proceed yet; filing to record the dependency.
Evidence
- pom.xml: <junit5.version>5.11.4</junit5.version> (via junit-bom),
<junit4.version>4.13.2</junit4.version>.
- pom.xml: <source.java.version>11</source.java.version> (some modules also
<target.java.version>11</target.java.version>).
- JUnit 6 requires a Java 17 baseline.
Blockers / prerequisites
- Flink still compiles source at Java 11 — hard blocker until the Java 11
baseline is dropped.
- FLINK-25325 (JUnit 4 → 5) must complete first; Vintage-run JUnit 4 tests
block a clean JUnit 6 adoption.
Proposed fix
- Bump junit-bom 5.x → 6.x once both blockers clear.
- Fix any removed/deprecated Jupiter APIs surfaced by the bump.
Acceptance
- Full build + test suite green on junit-bom 6.x.
- No remaining junit4.version / Vintage engine usage.
*This ticket is just for the placeholder of the JUnit6 migration. It can be
pursued till we have 17 as the default Java version. It would be smaller effort
and can be only build on top of JUnit5 migration.*
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
