[
https://issues.apache.org/jira/browse/NIFI-5318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16535702#comment-16535702
]
ASF GitHub Bot commented on NIFI-5318:
--------------------------------------
Github user peter-gergely-horvath commented on the issue:
https://github.com/apache/nifi/pull/2843
Hi @joewitt and @MikeThomsen I messed up this pull request with some
incorrectly merged code changes including the non-NiFi groupId and the
whitespace change in nifi-toolkit-tls module etc.
Sorry about that! For now, I will close any pull requests.
Since you had some really valuable ideas, could you please review the code
in https://github.com/peter-gergely-horvath/nifi/tree/master/nifi-testharness
and create issues with the inputs you have? I've implemented changes you
mentioned in this pull request there already.
> Implement NiFi test harness
> ---------------------------
>
> Key: NIFI-5318
> URL: https://issues.apache.org/jira/browse/NIFI-5318
> Project: Apache NiFi
> Issue Type: New Feature
> Reporter: Peter Horvath
> Priority: Major
>
> Currently, it is not really possible to automatically test the behaviour of a
> specific NiFi flow and make unit test type asserts if it works as expected.
> For example, if the expected behaviour of a NiFi flow is that a file placed
> to a specific directory will trigger some operation after which some output
> file will appear at another directory, once currently can only do one thing:
> test the NiFi flow manually.
> Manual testing is especially hard to manage if a NiFi flow is being actively
> developed: any change to a complex, existing NiFi flow might require a lot of
> manual testing just to ensure there are no regressions introduced.
> Some kind of Java API that allows managing a NiFi instance and manipulating
> flow deployments like for example, [Codehaus
> Cargo|]https://codehaus-cargo.github.io/] would be of great help.
>
>
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
