[
https://issues.apache.org/jira/browse/NIFI-34?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15855961#comment-15855961
]
Andre commented on NIFI-34:
---------------------------
Could the mvn checkstyle plugin to achieve this result?
https://maven.apache.org/plugins/maven-checkstyle-plugin/examples/custom-developed-checkstyle.html
> Mock Framework should provide option to detect common bad practices/bugs
> ------------------------------------------------------------------------
>
> Key: NIFI-34
> URL: https://issues.apache.org/jira/browse/NIFI-34
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Core Framework
> Reporter: Mark Payne
> Priority: Minor
>
> Mock Framework should detect common errors such as:
> * Processor has member variable that is a PropertyDescriptor, but the
> PropertyDescriptor isn't returned in the list of supported property
> descriptors.
> * Processor has member variable that is a Relationship, but the Relationship
> isn't returned in the Set of Relationships.
> * Processor has multiple properties or relationships as member variables with
> the same name.
> * No META-INF/services file
> * META-INF/services file doesn't contain the Component's Fully Qualified
> Class Name
> * No @CapabilityDescription annotation
> * No @Tags annotation
> Mock Framework should automatically detect these things and fail the unit
> test unless checking is disabled. This requires building an object that
> allows developer to enable/disable each of these checks.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
