[
https://issues.apache.org/jira/browse/NIFI-6183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16814858#comment-16814858
]
ASF subversion and git services commented on NIFI-6183:
-------------------------------------------------------
Commit 91b2283f49262b7d4c8a2fecbc757a360b0f8321 in nifi's branch
refs/heads/master from Mark Payne
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=91b2283 ]
NIFI-6183: Implemented base class for Framework-level integration tests that is
responsible for instantiating the key components for integration tests,
including FlowController, WriteAheadFlowFileRepository,
WriteAheadProvenanceRepository, FileSystemRepository, FileSystemSwapManager,
StandardFlowFileQueue, StandardProcessScheduler, etc. Implemented several
integration tests to span different parts of the framework
This closes #3423.
Signed-off-by: Bryan Bende <bbe...@apache.org>
> 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
> Time Spent: 40m
> 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)
