This may also affect JUnit4, I don't know.
Here's the build.gradle snippet
test {
useTestNG()
options {
includeGroups 'unit'
jvmArgs << "-Dnet.sourceforge.cobertura.datafile=${cobSerFile}"
}
}
Here's the resulting TestNG XML file:
<!DOCTYPE suite SYSTEM "http://testng.org/testng-1.0.dtd";>
<suite thread-count="5" skipfailedinvocationCounts="false" verbose="1"
name="Ant suite" junit="false" annotations="JDK"
data-provider-thread-count="10">
<test name="Ant test" junit="false">
<groups>
<run>
<include name="[unit]"/>
</run>
</groups>
<classes>
<class name="com.wjbradley.common.BusinessDateTimeTest"/>
</classes>
</test>
</suite>
None of my tests are being run because I have no "[unit]" group, but I
do have a "unit" group. When the testng.xml is build each entry in
the list needs to be in it's own include (without the brackets). It
looks like it may be doing this, but I'm not sure where the brackets
are coming from. There's also no unit test it looks like that tests
the group feature for testng. I spent about ten minutes digging, but
couldn't quickly see where this was happening.
--
Jason Porter
Real Programmers think better when playing Adventure or Rogue.
PGP key id: 926CCFF5
PGP fingerprint: 64C2 C078 13A9 5B23 7738 F7E5 1046 C39B 926C CFF5
PGP key available at: keyserver.net, pgp.mit.edu
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
