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

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

Github user MikeThomsen commented on a diff in the pull request:

    https://github.com/apache/nifi/pull/3165#discussion_r236045789
  
    --- Diff: nifi-testharness/src/test/resources/sample_technology_rss.xml ---
    @@ -0,0 +1,28 @@
    +
    +<?xml version="1.0" encoding="UTF-8"?>
    --- End diff --
    
    Yes, it absolutely must be changed because the BBC is asserting its IP 
rights here:
    
    ```
    <copyright><![CDATA[Copyright: (C) British Broadcasting Corporation, see 
http://news.bbc.co.uk/2/hi/help/rss/4498287.stm for terms and conditions of 
reuse.]]></copyright>
    ```


> 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