[
https://issues.apache.org/jira/browse/NIFI-1365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15116040#comment-15116040
]
Andy LoPresto commented on NIFI-1365:
-------------------------------------
No, we should remove those, they were artifacts from
https://issues.apache.org/jira/browse/NIFI-1364.
> Support Groovy unit tests
> -------------------------
>
> Key: NIFI-1365
> URL: https://issues.apache.org/jira/browse/NIFI-1365
> Project: Apache NiFi
> Issue Type: New Feature
> Components: Tools and Build
> Affects Versions: 0.4.1
> Reporter: Andy LoPresto
> Assignee: Andy LoPresto
> Labels: groovy, junit, spock, test
> Fix For: 0.5.0
>
>
> I posed a question on the dev mailing list about community enthusiasm for
> Groovy unit test support.
> {quote}
> I am considering writing unit tests in for new development/regression testing
> in Groovy. There are numerous advantages to this [1][2] (such as map
> coercion, relaxed permissions on dependency injection, etc.). Mocking large
> and complex objects, such as NiFiProperties, when only one feature is under
> test is especially easy. I plan to write “Java-style” unit tests, but this
> would also make TDD/BDD frameworks like Spock or Cucumber much easier to use.
> I figured before doing this I would poll the community and see if anyone
> strongly objects? In previous situations, I have created a custom Maven
> profile which only runs when triggered (by an environment variable, current
> username, etc.) to avoid polluting the environment of anyone who doesn’t want
> the Groovy test dependencies installed.
> Does anyone have thoughts on this?
> [1] http://www.ibm.com/developerworks/java/library/j-pg11094/index.html
> [2]
> https://keyholesoftware.com/2015/04/13/short-on-time-switch-to-groovy-for-unit-testing/
> {quote}
> The response was positive.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
