> This is:
>
> ******************************************************************
>
> <junitreport todir="${reports.xml.dir}">
> <fileset dir="${reports.xml.dir}">
> <include name="TEST-*.xml" />
> </fileset>
> <report format="frames" todir="${reports.html.dir}" />
> </junitreport>
>
> ******************************************************************
>
> David Saff escribió:
>
> Have you looked at the junitreport ant task?
>
> On Fri, Oct 23, 2009 at 10:16 AM, Tavo <
gtavo@...> wrote:
>
>
> Hi
> The test are running with ANT 1.7.1.
> This is the task
>
> ******************************************************************
> <junit fork="yes" failureProperty="test.failed" printsummary="on"
> haltonfailure="no">
> <!--
> Specify the name of the coverage data file to use.
> The value specified below is the default.
> -->
> <sysproperty key="net.sourceforge.cobertura.datafile"
> file="cobertura.ser" />
> <!--
> Note the classpath order: instrumented classes are before
> the
> original (uninstrumented) classes. This is important.
> -->
> <classpath location="${instrumented.dir}" />
> <classpath location="${classes.dir}" />
> <classpath location="${testclasses.dir}" />
> <classpath location="${testsrc.dir}" />
> <classpath location="${testlib.dir}" />
> <classpath path="${javac.test.classpath}" />
>
> <!--
> The instrumented classes reference classes used by the
> Cobertura runtime, so Cobertura and its dependencies
> must be on your classpath.
> -->
> <classpath refid="cobertura.classpath" />
>
> <!--
> Generete the XML report for merging with CruiseControl log.
> -->
> <formatter type="xml" />
> <batchtest todir="${reports.xml.dir}">
> <fileset dir="${testsrc.dir}">
> <include name="**/*TestSuite.java" />
> </fileset>
> </batchtest>
> </junit>
>
> ******************************************************************
> David Saff escribió:
>
> Tavo,
>
> How are you running the tests?
>
> David Saff
>
> On Thu, Sep 24, 2009 at 4:36 PM, Tavo <
gtavo@...> wrote:
>
>
> Hi
>
> After executing test based on TestSuites, the report detail shows
> only the name of the method executed, but not the class (*Test.java) it
> belongs. This make it very difficult to know exactly which test is
> failing, specially in classes like commands, where the only method is
> execute().
>
> We need to customize the reports generated by junit, so it can
> show the actual test class, instead (or besides) the testsuite class.
>
> Any advice will be much appreciated.
>
> Thanks,
> Tavo.
>
> ------------------------------------------------------------------------------
> Come build with us! The BlackBerry® Developer Conference in SF, CA
> is the only developer event you need to attend this year. Jumpstart your
> developing skills, take BlackBerry mobile applications to market and stay
> ahead of the curve. Join us from November 9-12, 2009. Register now!
>
http://p.sf.net/sfu/devconf> _______________________________________________
> Junit-devel mailing list
>
Junit-devel@...
>
https://lists.sourceforge.net/lists/listinfo/junit-devel>
>
>
> __________ Information from ESET Smart Security, version of virus signature
> database 4536 (20091023) __________
>
> The message was checked by ESET Smart Security.
>
>
http://www.eset.com>
>
>
>
>
>
> __________ Information from ESET Smart Security, version of virus signature
> database 4536 (20091023) __________
>
> The message was checked by ESET Smart Security.
>
>
http://www.eset.com>
>
>
> __________ Information from ESET Smart Security, version of virus signature
> database 4536 (20091023) __________
>
> The message was checked by ESET Smart Security.
>
>
http://www.eset.com>
>
>
>
>
>
> __________ Information from ESET Smart Security, version of virus signature
> database 4536 (20091023) __________
>
> The message was checked by ESET Smart Security.
>
>
http://www.eset.com>
is the only developer event you need to attend this year. Jumpstart your
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
