[
https://issues.apache.org/jira/browse/NIFI-9024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17397649#comment-17397649
]
David Handermann commented on NIFI-9024:
----------------------------------------
Hi [~jschneider], thanks for raising the issue and offering a way to migrate to
JUnit 5. NiFi has a very large number of unit tests, not all of which are
consistent in terms of JUnit usage, particularly when it comes to declaring
expected exceptions.
Other project maintainers may have more particular input, but it seems like an
incremental approach would be the best option. Right now, JUnit 4.13.2 is
included as a default dependency for all modules. For an initial step,
introducing the ability to use JUnit 5, and migrating a single selected module
would be a helpful proof of concept. That approach would also make it easier
to review the initial set of changes. A wholesale migration to JUnit 5 would be
a very large Pull Request, so what do you think about moving forward with an
initial implementation that maintains backwards compatibility with JUnit 4 as a
starting point?
> Upgrade from JUnit 4 to JUnit 5 Jupiter
> ---------------------------------------
>
> Key: NIFI-9024
> URL: https://issues.apache.org/jira/browse/NIFI-9024
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Core Framework
> Reporter: Jonathan K. Schneider
> Priority: Major
> Attachments: nifi.jpg
>
>
> Hi! I'm an author on [OpenRewrite|[https://github.com/openrewrite/rewrite],]
> an open source automated refactoring engine. I'd like to help do the work to
> move NIFI to JUnit 5 Jupiter from JUnit 4. We've done this on several other
> projects as well. Below is a sampling of a test migration on part of NIFI's
> code. Could we time the issuance of a PR with a NIFI maintainer's schedule to
> make this change?
> !nifi.jpg!
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
