Hi all, The behavior described in GRADLE-538 occures when there are no test classes, in this case both JUnit / TestNG tasks try to execute all classes as tests.
In order to solve this I'd like to skip test execution (calling of the JUnit / TestNG Ant tasks). This results in an empty JUnit report and no report in case of TestNG. The TestNG Ant task doesn't allow it to be run for no test classes, the Ant JUnit task does. So I'd like to add a GradleException when there are no test classes with a boolean to disable the exception (failWhenNoTests) default true. Currently when there are no test classes at all the build is ok in case of JUnit but in case of TestNG it fails, this is not really consistent, so we might want to straighten this out. This may cause a lot off builds to fail so I'd like to hear your optinions on this matter - to fail or not? Kr, Tom
