Thanks to everyone who weighed in. This feature is documented in NIFI-1365 [1] and there is a patch available [2].
The tests do not run by default and are triggered with a Java variable named `groovy` being set to `test`. It can be invoked as follows: `mvn clean test -Dgroovy=test` [1] https://issues.apache.org/jira/browse/NIFI-1365 <https://issues.apache.org/jira/browse/NIFI-1365> [2] https://github.com/apache/nifi/pull/163 <https://github.com/apache/nifi/pull/163> Andy LoPresto [email protected] PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4 BACE 3C6E F65B 2F7D EF69 > On Jan 10, 2016, at 6:06 AM, Joshua Davis <[email protected]> wrote: > > +1 Excellent idea > > Joshua Davis > Senior Consultant > Hortonworks Professional Services > (407)476-6752 > > > > > > > On 1/9/16, 11:52 AM, "Oleg Zhurakousky" <[email protected]> > wrote: > >> Big +1 >> >> Sent from my iPhone >> >> On Jan 4, 2016, at 18:30, Andy LoPresto >> <[email protected]<mailto:[email protected]>> wrote: >> >> 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/ >> >> >> Andy LoPresto >> [email protected]<mailto:[email protected]> >> PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4 BACE 3C6E F65B 2F7D EF69 >> >
signature.asc
Description: Message signed with OpenPGP using GPGMail
