On 27/03/10 5:33 AM, jashatton wrote:
I just figured it out. After re-reading the Test Task documentation I realized the search criteria for the test classes to run was based on classes that extend the TestCase class. I didn't expect that. I would think it is common that people would create base test cases that aren't run as part of the "suite".
Gradle will run any class it find which is not abstract and which extends TestCase, GroovyTestCase, or has a JUnit 4 annotation on it. There can be any number of levels of inheritance between the test class and TestCase or the class with the annotations on it. So, it is intended to handle exactly the case you describe.
However, the assumption is that the intermediate base classes are marked abstract, so Gradle will automatically exclude them. You've hit a bug where the excludes weren't wired up properly and were being ignored when there were no includes. This has been fixed in 0.9, and so should work as you expect (there's an integration test now, too). You can mark your base classes as abstract, or explicitly exclude them, or both, as you choose.
-- Adam Murdoch Gradle Developer http://www.gradle.org --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
