Currently the execution of test and test-single supports only testcases originating in java sources (*.java). Because of
that testcases written Groovy are not executed although these are valid JUnit testcases.
This is an ENH request. Although it might be important for Groovy I don't think we want to destabilize JUnit support for
java for this.
Related to issue #136835
Could we reconsider this? It's actually quite crucial to be able to run groovy tests and that's not possible with current build script..
Or is there any way to workarround this (e.g. overwrite some targets using groovy-build.xml file)?
In fact it is not needed now.
The J2SE Project has a merger for ActionProvider (issue #201737) in its Lookup and it can be extended using a custom AP.
Thats true and groovy support already has a custom AP implementation. The problem is that ant targets like -do-test-run doesn't expected something else than .java files and thus .groovy tests can't be executed.
AntBuildExtender should be ted in this case, see JavaFX or JavaWS.
Do I understand correctly that this bug wont be fixed?
Groovy is a tremendous help in producing *Java* tests with much less effort. This is a serious productivity issue for me but your mileage seems to vary.
I hope I have misunderstood and the bug is fixed with 7.2.
I'm a long time Netbeans user (since 4.0) and spread the "NB is great" word to all of my colleagues, I was willing to wait to 7.2 and keep writing tests in Java until 7.2. If this bugs wont be fixed I have to reevaluate which IDE to use :(
Right, it wont be fixed. It's not needed to implement the run test and test-single as described above.