I have a trivially small demonstration project. It is basically Java code so follows the Maven standard hierarchy for a Java project. The Gradle build for this works exactly as expected. I decided to add some Groovy tests to augment the Java tests. So I switched to using the Groovy plugin instead of the Java one and all the compilations happen as expected. All the Java tests get run, but the Groovy tests do not get run.
I am not sure what my current hypothesis is or should be. It is as though the Gradle tests finder searches the sources directories for names of test classes rather than searching the compiled classes directory. Has anyone got any pointers as to what might be going wrong, I am short of ideas. (I know the Groovy testcase code works as it runs fine if I run it manually with a Groovy command.) Thanks. -- Russel. ============================================================================= Dr Russel Winder t: +44 20 7585 2200 voip: sip:[email protected] 41 Buckmaster Road m: +44 7770 465 077 xmpp: [email protected] London SW11 1EN, UK w: www.russel.org.uk skype: russel_winder
signature.asc
Description: This is a digitally signed message part
