Description
Based on the consensus from the mailing list discussion[1][2], we have been starting working on the JUnit4 to JUnit5 migration.
This is the umbrella ticket which describes the big picture of the migration with following steps:
- AssertJ integration and guideline
- Test Framework upgrade from JUnit4 to JUnit5
- JUnit5 migration guideline(document and reference migration)
- Optimization for issues found while writing new test in JUint5
- [Long-term]Module based graceful migration of old tests in JUnit4 to JUnit5
All JUnit5 migration related tasks are welcome to be created under this umbrella.
Attachments
Issue Links
- duplicates
-
FLINK-23254 Upgrade Test Framework to JUnit 5
-
- Closed
-
- is a parent of
-
FLINK-23254 Upgrade Test Framework to JUnit 5
-
- Closed
-
-
FLINK-25858 Remove ArchUnit rules for JUnit 4 in ITCaseRules after the JUnit 4->5 migration is closed
-
- Open
-
-
FLINK-24627 Port JUnit 4 rules to JUnit5 extensions
-
- Closed
-
-
FLINK-26218 Enable JUnit 5 Automatic Extension Detection
-
- Closed
-
-
FLINK-25315 Add new extensions and classes to help the JUnit5 migration
-
- Resolved
-
-
FLINK-25061 Add assertj as dependency in flink-parent
-
- Closed
-