[
https://issues.apache.org/jira/browse/FLINK-25325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jing Ge updated FLINK-25325:
----------------------------
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
[1] [[DISCUSS]Moving to
JUnit5|https://lists.apache.org/thread/jsjvc2cqb91pyh47d4p6olk3c1vxqm3w]
[2] [[DISCUSS] Conventions on assertions to use in
tests|https://lists.apache.org/thread/33t7hz8w873p1bc5msppk65792z08rgt]
was:
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
[1]
[[DISCUSS]Moving to
JUnit5|https://lists.apache.org/thread/jsjvc2cqb91pyh47d4p6olk3c1vxqm3w]
[2] [[DISCUSS] Conventions on assertions to use in
tests|https://lists.apache.org/thread/33t7hz8w873p1bc5msppk65792z08rgt]
> Migration Flink from Junit4 to Junit5
> -------------------------------------
>
> Key: FLINK-25325
> URL: https://issues.apache.org/jira/browse/FLINK-25325
> Project: Flink
> Issue Type: New Feature
> Components: Tests
> Affects Versions: 1.14.0
> Reporter: Jing Ge
> Priority: Major
> Labels: Umbrella
> Fix For: 1.15.0
>
>
> 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
>
> [1] [[DISCUSS]Moving to
> JUnit5|https://lists.apache.org/thread/jsjvc2cqb91pyh47d4p6olk3c1vxqm3w]
> [2] [[DISCUSS] Conventions on assertions to use in
> tests|https://lists.apache.org/thread/33t7hz8w873p1bc5msppk65792z08rgt]
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
