[
https://issues.apache.org/jira/browse/NIFI-13625?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17871100#comment-17871100
]
Mark Payne commented on NIFI-13625:
-----------------------------------
I do agree we should avoid any use of System.out.println in unit tests, but
they should be changed to log statements, rather than System.out.println. We
should not remove log statements, as they do serve a purpose. The assertion
that "unit tests are for automated verification and not visual verification" I
would assert is incorrect. Automated verification is their primary purpose. But
when things fail, or updates are made, unit tests are relied upon VERY heavily
by the developers for debugging and verification.
While there is some overhead in I/O, that overhead should be trivial. If we
have tests generating so much I/O from logging that it has an performance
concern then that particular test should certainly be looked into, as the
logging is likely not very helpful at those volumes anyway.
> Remove System.out.println and logging statements from unit and integration
> testing
> ----------------------------------------------------------------------------------
>
> Key: NIFI-13625
> URL: https://issues.apache.org/jira/browse/NIFI-13625
> Project: Apache NiFi
> Issue Type: Improvement
> Reporter: Daniel Stieglitz
> Assignee: Daniel Stieglitz
> Priority: Minor
>
> Remove all System.out.println statements from unit and integration tests as
> well as all logging statements which are purely for visual confirmation.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)