[jira] [Updated] (FLINK-25325) Migration Flink from Junit4 to Junit5
[ 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 All JUnit5 migration related tasks are welcome to be created under this umbrella. [https://github.com/apache/flink/pull/24483] is an excellent PR as example. Please create similar Brief change log summary for new PR. [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] [3] [JUnit5 migration guide|https://docs.google.com/document/d/1514Wa_aNB9bJUen4xm5uiuXOooOJTtXqS_Jqk9KJitU/edit] 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 All JUnit5 migration related tasks are welcome to be created under this umbrella. [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] [3] [JUnit5 migration guide|https://docs.google.com/document/d/1514Wa_aNB9bJUen4xm5uiuXOooOJTtXqS_Jqk9KJitU/edit] > 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.20.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 > All JUnit5 migration related tasks are welcome to be created under this > umbrella. > > [https://github.com/apache/flink/pull/24483] is an excellent PR as example. > Please create similar Brief change log summary for new PR. > > [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] > [3] [JUnit5 migration > guide|https://docs.google.com/document/d/1514Wa_aNB9bJUen4xm5uiuXOooOJTtXqS_Jqk9KJitU/edit] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FLINK-25325) Migration Flink from Junit4 to Junit5
[ https://issues.apache.org/jira/browse/FLINK-25325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] lincoln lee updated FLINK-25325: Fix Version/s: (was: 1.19.0) > 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.20.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 > > All JUnit5 migration related tasks are welcome to be created under this > umbrella. > > > [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] > [3] [JUnit5 migration > guide|https://docs.google.com/document/d/1514Wa_aNB9bJUen4xm5uiuXOooOJTtXqS_Jqk9KJitU/edit] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FLINK-25325) Migration Flink from Junit4 to Junit5
[ https://issues.apache.org/jira/browse/FLINK-25325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] lincoln lee updated FLINK-25325: Fix Version/s: 1.20.0 > 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.19.0, 1.20.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 > > All JUnit5 migration related tasks are welcome to be created under this > umbrella. > > > [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] > [3] [JUnit5 migration > guide|https://docs.google.com/document/d/1514Wa_aNB9bJUen4xm5uiuXOooOJTtXqS_Jqk9KJitU/edit] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FLINK-25325) Migration Flink from Junit4 to Junit5
[ https://issues.apache.org/jira/browse/FLINK-25325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jing Ge updated FLINK-25325: Fix Version/s: 1.19.0 (was: 1.18.0) > 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.19.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 > > All JUnit5 migration related tasks are welcome to be created under this > umbrella. > > > [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] > [3] [JUnit5 migration > guide|https://docs.google.com/document/d/1514Wa_aNB9bJUen4xm5uiuXOooOJTtXqS_Jqk9KJitU/edit] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FLINK-25325) Migration Flink from Junit4 to Junit5
[ https://issues.apache.org/jira/browse/FLINK-25325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xintong Song updated FLINK-25325: - Fix Version/s: 1.18.0 (was: 1.17.0) > 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.18.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 > > All JUnit5 migration related tasks are welcome to be created under this > umbrella. > > > [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] > [3] [JUnit5 migration > guide|https://docs.google.com/document/d/1514Wa_aNB9bJUen4xm5uiuXOooOJTtXqS_Jqk9KJitU/edit] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FLINK-25325) Migration Flink from Junit4 to Junit5
[ https://issues.apache.org/jira/browse/FLINK-25325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xingbo Huang updated FLINK-25325: - Fix Version/s: 1.17.0 (was: 1.16.0) > 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.17.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 > > All JUnit5 migration related tasks are welcome to be created under this > umbrella. > > > [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] > [3] [JUnit5 migration > guide|https://docs.google.com/document/d/1514Wa_aNB9bJUen4xm5uiuXOooOJTtXqS_Jqk9KJitU/edit] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FLINK-25325) Migration Flink from Junit4 to Junit5
[ https://issues.apache.org/jira/browse/FLINK-25325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yun Gao updated FLINK-25325: Fix Version/s: 1.16.0 > 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, 1.16.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 > > All JUnit5 migration related tasks are welcome to be created under this > umbrella. > > > [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] > [3] [JUnit5 migration > guide|https://docs.google.com/document/d/1514Wa_aNB9bJUen4xm5uiuXOooOJTtXqS_Jqk9KJitU/edit] -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (FLINK-25325) Migration Flink from Junit4 to Junit5
[ 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 All JUnit5 migration related tasks are welcome to be created under this umbrella. [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] [3] [JUnit5 migration guide|https://docs.google.com/document/d/1514Wa_aNB9bJUen4xm5uiuXOooOJTtXqS_Jqk9KJitU/edit] 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 All JUnit5 migration related tasks are welcome to be created under this umbrella. [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] [3][JUnit5 migration guide |[https://docs.google.com/document/d/1514Wa_aNB9bJUen4xm5uiuXOooOJTtXqS_Jqk9KJitU/edit]] > 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 > > All JUnit5 migration related tasks are welcome to be created under this > umbrella. > > > [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] > [3] [JUnit5 migration > guide|https://docs.google.com/document/d/1514Wa_aNB9bJUen4xm5uiuXOooOJTtXqS_Jqk9KJitU/edit] -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (FLINK-25325) Migration Flink from Junit4 to Junit5
[ 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 All JUnit5 migration related tasks are welcome to be created under this umbrella. [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] [3][JUnit5 migration guide |[https://docs.google.com/document/d/1514Wa_aNB9bJUen4xm5uiuXOooOJTtXqS_Jqk9KJitU/edit]] 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 All JUnit5 migration related tasks are welcome to be created under this umbrella. [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 > > All JUnit5 migration related tasks are welcome to be created under this > umbrella. > > > [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] > [3][JUnit5 migration guide > |[https://docs.google.com/document/d/1514Wa_aNB9bJUen4xm5uiuXOooOJTtXqS_Jqk9KJitU/edit]] > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (FLINK-25325) Migration Flink from Junit4 to Junit5
[ 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 All JUnit5 migration related tasks are welcome to be created under this umbrella. [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 > > All JUnit5 migration related tasks are welcome to be created under this > umbrella. > > [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)
[jira] [Updated] (FLINK-25325) Migration Flink from Junit4 to Junit5
[ 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)
