title: Gradle compiles but does not run TestNG tests
body: <p>We just started using Gradle and TestNG on our project, so I am checking whether failing any test actually fails the build. I was quite surprised to see it does not. The tests are picked up and compiled correctly, so I see the class files. Also I do get a report of the run, but it says 0 tests (expected 2). Running <code>gradle clean test -i</code> gives me the following:</p>
  
  <pre><code>:contentplatform-service:compileTestJava (Thread[Daemon worker Thread 7,5,main])
   started.
  :contentplatform-service:compileTestJava
  Executing task ':contentplatform-service:compileTestJava' (up-to-date check took
   0.08 secs) due to:
    Output file D:\Dev\contentplatform-service\build\classes\test has changed.
    Output file D:\Dev\contentplatform-service\build\dependency-cache has changed.
  
    Output file D:\Dev\contentplatform-service\build\classes\test\nl\xillio\conten
  tplatform\service\SuperSimpleTest.class has been removed.
  All input files are considered out-of-date for incremental task ':contentplatfor
  m-service:compileTestJava'.
  Compiling with JDK Java compiler API.
  :contentplatform-service:compileTestJava (Thread[Daemon worker Thread 7,5,main])
   completed. Took 0.229 secs.
  :contentplatform-service:processTestResources (Thread[Daemon worker Thread 7,5,m
  ain]) started.
  :contentplatform-service:processTestResources
  Skipping task ':contentplatform-service:processTestResources' as it has no sourc
  e files.
  :contentplatform-service:processTestResources UP-TO-DATE
  :contentplatform-service:processTestResources (Thread[Daemon worker Thread 7,5,m
  ain]) completed. Took 0.001 secs.
  :contentplatform-service:testClasses (Thread[Daemon worker Thread 7,5,main]) sta
  rted.
  :contentplatform-service:testClasses
  Skipping task ':contentplatform-service:testClasses' as it has no actions.
  :contentplatform-service:testClasses (Thread[Daemon worker Thread 7,5,main]) com
  pleted. Took 0.001 secs.
  :contentplatform-service:test (Thread[Daemon worker Thread 7,5,main]) started.
  :contentplatform-service:test
  Executing task ':contentplatform-service:test' (up-to-date check took 0.049 secs
  ) due to:
    Output file D:\Dev\contentplatform-service\build\test-results\binary\test has
  changed.
    Output file D:\Dev\contentplatform-service\build\test-results has changed.
    Output file D:\Dev\contentplatform-service\build\reports\tests has changed.
  Finished generating test XML results (0.0 secs) into: D:\Dev\contentplatform-ser
  vice\build\test-results
  Generating HTML test report...
  Finished generating test html results (0.014 secs) into: D:\Dev\contentplatform-
  service\build\reports\tests
  :contentplatform-service:test (Thread[Daemon worker Thread 7,5,main]) completed.
   Took 0.194 secs.
  </code></pre>
  
  <p>SuperSimpleTest.java:</p>
  
  <pre><code>package nl.xillio.contentplatform.service;
  
  import org.testng.Assert;
  import org.testng.annotations.BeforeClass;
  import org.testng.annotations.Test;
  
  @Test
  public class SuperSimpleTest {
  
      @BeforeClass
      public void setUp() {
          // code that will be invoked when this test is instantiated
      }
  
      @Test
      public void testTest() {
          Assert.assertEquals(true, true);
      }
  }
  </code></pre>
  
  <p>build.gradle contains:</p>
  
  <pre><code>test {
      // enable TestNG support (default is JUnit)
      useTestNG()
      scanForTestClasses = false  
      include '**/*'
  
      testLogging {
          showStandardStreams = true
  
          // log results to "build/test-results" directory
          exceptionFormat "full"
          events "started", "passed", "skipped", "failed", "standardOut", "standardError"
      }
  }
  </code></pre>
  
  <p>I already took a look at <a href="https://stackoverflow.com/questions/28008918/gradle-not-running-testng-tests-even-with-test-usetestng/28077602#28077602">other questions</a> about this topic, and there I found the hint to use <code>scanForTestClasses = false</code> as a workaround (see <a href="https://issues.gradle.org/browse/GRADLE-1682" rel="noreferrer">https://issues.gradle.org/browse/GRADLE-1682</a>). However, this problem seems unrelated. Am I making some other noob mistake here? How can I get SuperSimpleTest to just execute?</p>
  
  <p>UPDATE: I tried forcing gradle to run a specific test with an interesting error as a result: <a href="https://stackoverflow.com/questions/28169332/gradle-complains-about-junit-version-on-testng-task">Gradle complains about JUnit version on TestNG task</a></p>