Hey Rene, It turns out that adding the closure you mentioned was all that was necessary.
I will now be trying to do fancy things like adding tasks for running only unit tests and running only integration tests, but let's see if I can do these by myself! Thanks so much for your help. -----Original Message----- From: Rene Groeschke [mailto:[email protected]] Sent: Wednesday, February 02, 2011 7:21 PM To: [email protected] Subject: Re: [gradle-user] Gradle Not Finding My Tests Hi Neil, are your test files compiled correctly? I'm not an experienced testng user, but did you configure your test task to use testng? I'm not sure if this is still needed, but did you add ------- test{ useTestNG() } ------- to your build? regards, René Am 03.02.11 00:49, schrieb Neil Chaudhuri: > I am an experienced Java developer and Maven user, and I am evaluating Gradle > for a possible transition. So far I have my multi-module project building > nicely and quite cleanly, but when I run "gradle test," Gradle isn't finding > any of my test classes. My layout follows the Maven, and I thought Gradle, > conventions precisely: > > --myproj > ----build.gradle > ----src > ----main > ----java > ----resources > ----test > ----java > ---------------Test source all here > ----resources > > After studying the manual, I figured that the testing sourceSet defaulted to > what I have above, but perhaps I was wrong. Any insight into whatever silly > thing I have misconfigured is appreciated. > > Thanks. > > > -- ------------------------------------ Rene Groeschke [email protected] http://www.breskeby.com http://twitter.com/breskeby ------------------------------------ --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
