[
https://issues.apache.org/jira/browse/FLINK-25540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17753071#comment-17753071
]
Matthias Pohl commented on FLINK-25540:
---------------------------------------
That makes sense to have the efforts reflected in Jira as well. Another
approach would be to migrate test classes when actually touching them as part
of some other work (and include the migration as a separate commit in that
unrelated PR). That's how I dealt with the JUnit5 migration in the past. But
this approach takes longer. In the end, it's a bit of both that brings us to
the finish line, I guess. Therefore, thanks for picking it up.
> [JUnit5 Migration] Module: flink-runtime
> ----------------------------------------
>
> Key: FLINK-25540
> URL: https://issues.apache.org/jira/browse/FLINK-25540
> Project: Flink
> Issue Type: Sub-task
> Components: Tests
> Reporter: Hang Ruan
> Assignee: RocMarshal
> Priority: Minor
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
