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

Daniel Stieglitz updated NIFI-15506:
------------------------------------
    Description: 
It seems the use of classes
{code:java}
nifi-extension-bundles/nifi-standard-services/nifi-lookup-services-bundle/nifi-lookup-services/src/test/java/org/apache/nifi/lookup/TestProcessor.java
 
{code}
{code:java}
nifi-extension-bundles/nifi-aws-bundle/nifi-aws-processors/src/test/java/org/apache/nifi/processors/aws/credentials/provider/service/MockAWSProcessor.java
{code}
{code:java}
nifi-extension-bundles/nifi-standard-services/nifi-record-serialization-services-bundle/nifi-record-serialization-services/src/test/java/org/apache/nifi/serialization/TestRecordReaderProcessor.java{code}
{code:java}
nifi-extension-bundles/nifi-standard-services/nifi-record-serialization-services-bundle/nifi-record-serialization-services/src/test/java/org/apache/nifi/serialization/TestRecordSetWriterProcessor.java{code}
 
{code:java}
nifi-extension-bundles/nifi-standard-services/nifi-record-sink-service-bundle/nifi-record-sink-service/src/test/java/org/apache/nifi/record/sink/TestProcessor.java
{code}
to test controller services or the use of
{code:java}
Mockito.mock(Processor.class){code}
are not necessary as org.apache.nifi.util.NoOpProcessor fits the same purpose.

  was:
It seems the use of classes
{code:java}
nifi-extension-bundles/nifi-standard-services/nifi-lookup-services-bundle/nifi-lookup-services/src/test/java/org/apache/nifi/lookup/TestProcessor.java
 
{code}
{code:java}
nifi-extension-bundles/nifi-aws-bundle/nifi-aws-processors/src/test/java/org/apache/nifi/processors/aws/credentials/provider/service/MockAWSProcessor.java
{code}
{code:java}
nifi-extension-bundles/nifi-standard-services/nifi-record-serialization-services-bundle/nifi-record-serialization-services/src/test/java/org/apache/nifi/serialization/TestRecordReaderProcessor.java{code}
{code:java}
nifi-extension-bundles/nifi-standard-services/nifi-record-serialization-services-bundle/nifi-record-serialization-services/src/test/java/org/apache/nifi/serialization/TestRecordSetWriterProcessor.java{code}
to test controller services or the use of
{code:java}
Mockito.mock(Processor.class){code}
are not necessary as org.apache.nifi.util.NoOpProcessor fits the same purpose.


> Replace shell processor test classes used to test  controller services with 
> org.apache.nifi.util.NoOpProcessor
> --------------------------------------------------------------------------------------------------------------
>
>                 Key: NIFI-15506
>                 URL: https://issues.apache.org/jira/browse/NIFI-15506
>             Project: Apache NiFi
>          Issue Type: Improvement
>            Reporter: Daniel Stieglitz
>            Assignee: Daniel Stieglitz
>            Priority: Minor
>
> It seems the use of classes
> {code:java}
> nifi-extension-bundles/nifi-standard-services/nifi-lookup-services-bundle/nifi-lookup-services/src/test/java/org/apache/nifi/lookup/TestProcessor.java
>  
> {code}
> {code:java}
> nifi-extension-bundles/nifi-aws-bundle/nifi-aws-processors/src/test/java/org/apache/nifi/processors/aws/credentials/provider/service/MockAWSProcessor.java
> {code}
> {code:java}
> nifi-extension-bundles/nifi-standard-services/nifi-record-serialization-services-bundle/nifi-record-serialization-services/src/test/java/org/apache/nifi/serialization/TestRecordReaderProcessor.java{code}
> {code:java}
> nifi-extension-bundles/nifi-standard-services/nifi-record-serialization-services-bundle/nifi-record-serialization-services/src/test/java/org/apache/nifi/serialization/TestRecordSetWriterProcessor.java{code}
>  
> {code:java}
> nifi-extension-bundles/nifi-standard-services/nifi-record-sink-service-bundle/nifi-record-sink-service/src/test/java/org/apache/nifi/record/sink/TestProcessor.java
> {code}
> to test controller services or the use of
> {code:java}
> Mockito.mock(Processor.class){code}
> are not necessary as org.apache.nifi.util.NoOpProcessor fits the same purpose.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to