nifi-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brandon DeVries (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (NIFI-773) Mock Framework needs to provide better mechanisms for testing Controller Services
Date Fri, 04 Sep 2015 17:16:45 GMT

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

Brandon DeVries commented on NIFI-773:
--------------------------------------

this comment will probably be OBE after the creation of a ControllerService-specific Test
Runner, but under the current model a controller service's customValidate() method isn't called
until after the methods annotated with \@onEnabled, which can cause some unexpected behavior.

> Mock Framework needs to provide better mechanisms for testing Controller Services
> ---------------------------------------------------------------------------------
>
>                 Key: NIFI-773
>                 URL: https://issues.apache.org/jira/browse/NIFI-773
>             Project: Apache NiFi
>          Issue Type: Task
>          Components: Tools and Build
>            Reporter: Mark Payne
>
> Currently, in order to test a Controller Service with the TestRunner, you have to create
the TestRunner by creating a mocked out Processor.
> We need to provide the ability to test Controller Services without doing this type of
thing.
> Additionally, we then have to set properties by calling TestRunner.setProperty(ControllerService,
PropertyDescriptor, String). This is fine if we are using a Controller Service to test a processor,
but if the Controller Service itself is what is being tested, there should be no need to pass
the controller service to the test runner each time.
> Recommend we create a ControllerService-specific Test Runner.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message