[
https://issues.apache.org/jira/browse/NIFI-5436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16546892#comment-16546892
]
ASF GitHub Bot commented on NIFI-5436:
--------------------------------------
Github user ottobackwards commented on a diff in the pull request:
https://github.com/apache/nifi/pull/2902#discussion_r203102528
--- Diff: nifi-docs/src/main/asciidoc/developer-guide.adoc ---
@@ -2144,9 +2144,10 @@ you can use the Maven dependency:
</dependency>
----
-We create a new `TestRunner` by calling the static `newTestRunner` method
of the `TestRunners` class
-(located in the `org.apache.nifi.util` package). This method takes a
single argument. That argument can
-either be the class of the Processor to test or can be an instance of a
Processor.
+We create a new `TestRunner` by calling on of the static `newTestRunner`
methods of the `TestRunners` class
--- End diff --
oops. sorry. fixed.
> TestRunner should allow setting the processor name
> --------------------------------------------------
>
> Key: NIFI-5436
> URL: https://issues.apache.org/jira/browse/NIFI-5436
> Project: Apache NiFi
> Issue Type: Improvement
> Reporter: Otto Fowler
> Assignee: Otto Fowler
> Priority: Major
>
> Currently, the ProcessContext.getName() just returns a blank String. Some
> users use that value of the context, but cannot test their processors
> properly because there is no way to set this value.
>
> The TestRunner down to the MockProcessContext should support setting the name
> of the processor when you create the TestRunner instance.
>
> If no name is provided, the the Processor class name should be used.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
