[
https://issues.apache.org/jira/browse/NIFI-5318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16627563#comment-16627563
]
ASF GitHub Bot commented on NIFI-5318:
--------------------------------------
Github user peter-gergely-horvath commented on the issue:
https://github.com/apache/nifi/pull/2872
Hi @MikeThomsen I _intentionally_ have no test configuration in the project
(at least for now): they are merely *samples* of what can be done, but they
should not be executed as part of the core NiFi build.
NiFi is a beast, starting and stopping it takes some time, I do not want to
add that to the each NiFi build.
Please create a new Maven project quickstart project (that will have
testing configuration enabled) and add the following (replacing `${nifi
version}` with the current one) to the dependencies:
```
<dependency>
<groupId>org.apache.nifi:</groupId>
<artifactId>nifi-testharness</artifactId>
<version>${nifi version}</version>
</dependency>
```
once done, you can take the samples into your own project, where you can
experiment with the test harness.
I understand piggybacking on the tests directory is maybe not the perfect
place to deliver samples, but given the circumstances I think it is acceptable
and could maybe be improved in the future.
> 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)
