[ https://issues.apache.org/jira/browse/NIFI-5318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16665467#comment-16665467 ]
ASF GitHub Bot commented on NIFI-5318: -------------------------------------- Github user peter-gergely-horvath commented on the issue: https://github.com/apache/nifi/pull/2872 @MikeThomsen This is kind of tricky: NiFi flows refer the precise version of NiFi within the flow XML file, so you have something like this for the processor definitions: ``` <class>org.apache.nifi.processors.standard.GetHTTP</class> <bundle> <group>org.apache.nifi</group> <artifact>nifi-standard-nar</artifact> <version>1.7.1</version> </bundle> ``` When you export a flow file to test, I would expect the you to use precisely the same NiFi version as the one used to export the flow file. I think there is a little bit of confusion here: please note that these tests do not test the test-harness. The test-harness itself is not tested (kind of a chicken-and-egg issue): these test cases are merely _samples_, which are referenced in the documentation: they demonstrate how an _end-user_ could create test cases for his/her own flows. Please download the ZIP of NiFi 1.7.1 to the `Downloads` directory within your user home (referenced by `org.apache.nifi.testharness.samples.Constants#NIFI_ZIP_DIR` as `new File(System.getProperty("user.home"), "Downloads")` ) and try running the test case again. > 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)