[
https://issues.apache.org/jira/browse/NIFI-11035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17680368#comment-17680368
]
ASF subversion and git services commented on NIFI-11035:
--------------------------------------------------------
Commit 53371844a418c9c7807f66a63d08a50856641750 in nifi's branch
refs/heads/main from dan-s1
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=53371844a4 ]
NIFI-11035 Replaced remaining JUnit 4 assertions in nifi-commons with JUnit 5
- Replaced Groovy asserts with JUnit 5 assertions and Groovy shouldFail method
Junit 5 with assertThrow method
This closes #6880
Signed-off-by: David Handermann <[email protected]>
> Replace remaining JUnit 4 assertions in nifi-commons with JUnit 5 assertions
> ----------------------------------------------------------------------------
>
> Key: NIFI-11035
> URL: https://issues.apache.org/jira/browse/NIFI-11035
> Project: Apache NiFi
> Issue Type: Sub-task
> Reporter: Daniel Stieglitz
> Assignee: Daniel Stieglitz
> Priority: Minor
> Time Spent: 20m
> Remaining Estimate: 0h
>
> A quick search nifi-commons for "org.junit.Assert" indicates there are over
> 50 cases where JUnit 4 assertions are still being used. These should be
> replaced with JUnit 5 assertions. In addition all Groovy assert statements
> should be replaced with appropriate JUnit 5 assertions and all instances of
> Groovy shouldFail method should be replaced with JUnit5 assertThrows.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
