Hi, On Fri, Mar 14, 2014 at 12:37 AM, Chetan Mehrotra <[email protected]> wrote: > I need to write couple of integration testcase related to checking > OSGi configuration support (OAK-1502) in oak-pojosr module. It would > be much much more faster and convenient for me if I can write these > testcases in groovy. > > So would it be fine if I can use Groovy language for writing testcase > only in oak-pojosr module?
No objections from me. We had a related discussion two years ago (see http://markmail.org/message/fbidi5wxl5czrkgi) and the rough consensus back then was to stick with Java for the most part, but remain open for alternatives in auxiliary code like isolated plugins, test cases and tooling. So far we've done this only with a few perl and shell scripts. Just note that the choice of language may deter contributions from others. For example the analyze-hprof.pl script isn't too friendly to people without background in perl, but when writing it I considered that the ease of implementation for me outweighed the drawbacks, as the tool is rather self-contained, not too heavily used and won't need much maintenance. It sounds like the tradeoff for the test code you're considering may be similar. BR, Jukka Zitting
