You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@nifi.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2019/03/16 14:10:01 UTC

[jira] [Commented] (NIFI-5318) Implement NiFi test harness

    [ https://issues.apache.org/jira/browse/NIFI-5318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16794261#comment-16794261 ] 

ASF subversion and git services commented on NIFI-5318:
-------------------------------------------------------

Commit 43235724e2031c30fc48e05be0d2136fd58efa52 in nifi's branch refs/heads/master from Peter G. Horvath
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=4323572 ]

NIFI-5318 Implement NiFi test harness: initial commit
NIFI-5318 Implement NiFi test harness: replaced original sample feed payload with synthetic content
NIFI-5318 Implement NiFi test harness: fixed test harness run crash issue; better reporting of paths
NIFI-5318 Implement NiFi test harness: added further states where NiFi version can be queried
NIFI-5318 Implement NiFi test harness: fixed incorrect class reference
NIFI-5318 Implement NiFi test harness: added type parameter bounding to setClassOfSingleProcessor to prevent configuring obviously incorrect classes
NIFI-5318 Updated project version.

This closes #3165

Signed-off-by: Mike Thomsen <mi...@gmail.com>


> 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
>          Time Spent: 1h 50m
>  Remaining Estimate: 0h
>
> 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)