Hello Hans,
hdockter wrote: > > I don't know how the JetBrains guys hook into into this for there Ant > Teamcity runner. > I've read that they use a patched Ant JUnit task. hdockter wrote: > > What we want to do for 0.6 is to rewrite our Test task to natively > run the tests. Then we can provide listeners for test execution. > Do you plan to provide test isolation similar to Ant's/Maven's fork mode? If yes, will I be able to register a test execution listener even if the tests are run in a different VM? A different approach would be to parse JUnit's XML report, but I'd prefer to avoid that if possible. What do you think? Guess I'll give it another try when Gradle 0.6 is out. By that time, the SPI of TeamCity 4 will probably have stabilized as well. Cheers, Peter -- View this message in context: http://www.nabble.com/How-to-track-JUnit-test-execution-tp20253541p20269048.html Sent from the gradle-user mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
