Hi,

I have an abstract base test class. It looks like this:

public abstract class BaseJkTest extends TestCase {
   ...
}

The issue is that the gradle build fails with:

No tests found in jk.util.BaseJkTest
junit.framework.AssertionFailedError: No tests found in jk.util.BaseJkTest

But shouldn't abstract classes being excluded from the JUnit tests in the first place? I remember that the Maven surefire plug-in excluded those classes automatically. When I rename my test to AbstractBaseJkTest everything works fine. I am just wondering if it is possible to improve gradle in a way that it detects abstract classes automatically (and not just by naming conventions)? Anyway renaming the class solved my problem for now. Just wanted to mention this potential problem.

Btw, I am running gradle 0.5.2.

Thanks for any help,
--Peter

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

   http://xircles.codehaus.org/manage_email


Reply via email to