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

Posted to issues@nifi.apache.org by "Bryan Bende (JIRA)" <ji...@apache.org> on 2019/04/10 20:54:00 UTC

[jira] [Resolved] (NIFI-6183) Improve Framework's Integration Tests

     [ https://issues.apache.org/jira/browse/NIFI-6183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bryan Bende resolved NIFI-6183.
-------------------------------
       Resolution: Fixed
    Fix Version/s: 1.10.0

> Improve Framework's Integration Tests
> -------------------------------------
>
>                 Key: NIFI-6183
>                 URL: https://issues.apache.org/jira/browse/NIFI-6183
>             Project: Apache NiFi
>          Issue Type: Test
>          Components: Core Framework
>            Reporter: Mark Payne
>            Assignee: Mark Payne
>            Priority: Major
>             Fix For: 1.10.0
>
>          Time Spent: 50m
>  Remaining Estimate: 0h
>
> NiFi's framework has a lot of unit tests and several integration tests. However, the integration tests tend to focus on integration between to specific components (e.g., the content repo and flowfile repo). It would be beneficial to provide integration tests between all of the "real" components in the framework, almost to the point of standing up a full NiFi instance.
> For example, we should provide integration tests that make use of FileSystemRepository, WriteAheadFlowFileRepository, WriteAheadProvenanceRepository, StandardProcessSession, FlowController, StandardProcessScheduler, StandardFlowFileQueue, FileSystemSwapManger, etc.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)