Hi Peter,
On Jan 28, 2009, at 8:04 PM, Peter Voss wrote:
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.
You are right. This is planned for 0.6 or 0.7. There is also an issue
for this: http://jira.codehaus.org/browse/GRADLE-281. In 0.5.x we
delegate to the ant junit runner, which is not capable of this.
- Hans
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
--
Hans Dockter
Gradle Project lead
http://www.gradle.org
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
