[
https://issues.apache.org/jira/browse/NIFI-1213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15284983#comment-15284983
]
ASF GitHub Bot commented on NIFI-1213:
--------------------------------------
Github user olegz commented on the pull request:
https://github.com/apache/nifi/pull/404#issuecomment-219502908
@pvillard31 there is a merge conflict in
```
CONFLICT (content): Merge conflict in
nifi-mock/src/test/java/org/apache/nifi/util/TestStandardProcessorTestRunner.java
```
Could you please take care of it?
> Allow Mock Framework to register "FlowFile Assertions"
> ------------------------------------------------------
>
> Key: NIFI-1213
> URL: https://issues.apache.org/jira/browse/NIFI-1213
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Tools and Build
> Reporter: Mark Payne
> Assignee: Pierre Villard
> Fix For: 1.0.0, 0.7.0
>
>
> Often times, unit tests will invoke TestRunner.run, and then iterate through
> the output FlowFiles, ensuring that a particular attribute exists, or that an
> attribute is equal to some value.
> As a convenience, we should provide a mechanism to indicate that all output
> FlowFiles (or all FlowFiles routed to a given relationship) meet some
> criteria.
> For example:
> {code}
> TestRunner.assertAllFlowFilesContainAttribute( String attributeName );
> {code}
> {code}
> TestRunner.assertAllFlowFilesContainAttribute( Relationship relationship,
> String attributeName );
> {code}
> Additionally, we should consider allowing a "callback" mechanism:
> {code}
> TestRunner.assertAllFlowFiles( FlowFileValidator validator );
> {code}
> {code}
> TestRunner.assertAllFlowFiles( Relationship relationship, FlowFileValidator
> validator );
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
