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

ASF GitHub Bot commented on NIFI-5318:
--------------------------------------

Github user peter-gergely-horvath commented on the issue:

    https://github.com/apache/nifi/pull/2843
  
    @MikeThomsen I tried, but it kept failing with other tests cases, unrelated 
to my changes, see above in pull request: 
    ```
    At the moment, the build fails with unit test failures unrelated to this 
commit:
    [INFO] Running org.apache.nifi.csv.TestCSVValidators
    [INFO] Tests run: 7, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.018 s - in org.apache.nifi.csv.TestCSVValidators
    [INFO] Running org.apache.nifi.csv.TestJacksonCSVRecordReader
    [ERROR] Tests run: 11, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 
0.033 s <<< FAILURE! - in org.apache.nifi.csv.TestJacksonCSVRecordReader
    [ERROR] testUTF8(org.apache.nifi.csv.TestJacksonCSVRecordReader)  Time 
elapsed: 0.002 s  <<< FAILURE!
    org.junit.ComparisonFailure: expected:<[黃凱揚]> but was:<[???]>
        at org.apache.nifi.csv.TestJacksonCSVRecordReader.testUTF8(TestJ
    ```
    
    The fact I cannot get a working build from original/master is kind of 
painful, do you see any way for me to remedy this?


> 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)

Reply via email to