Re: Junit Report

Have you looked at the junitreport ant task?

On Fri, Oct 23, 2009 at 10:16 AM, Tavo <[email protected]> wrote:
> Hi
> =A0=A0=A0=A0=A0 The test are running with ANT 1.7.1.
> This is the task
>
> ******************************************************************
> <junit fork=3D"yes" failureProperty=3D"test.failed"=A0 printsummary=3D"on"
> haltonfailure=3D"no">
> =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 <!--
> =A0=A0=A0 =A0=A0=A0 Specify the name of the coverage data file to use.
> =A0=A0=A0 =A0=A0=A0 The value specified below is the default.
> =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 -->
> =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 <sysproperty key=3D"net.sourceforge.cob=
ertura.datafile"
> =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 =
file=3D"cobertura.ser" />
> =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 <!--
> =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 Note the classpath order: i=
nstrumented classes are before
> the
> =A0=A0=A0 =A0=A0=A0 original (uninstrumented) classes.=A0 This is importa=
nt.
> =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 -->
> =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 <classpath location=3D"${instrumented.d=
ir}" />
> =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 <classpath location=3D"${classes.dir}" =
/>
> =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 <classpath location=3D"${testclasses.di=
r}" />
> =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 <classpath location=3D"${testsrc.dir}" =
/>
> =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 <classpath location=3D"${testlib.dir}" =
/>
> =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 <classpath path=3D"${javac.test.classpa=
th}" />
>
> =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 <!--
> =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 The instrumented classes re=
ference classes used by the
> =A0=A0=A0 =A0=A0=A0 Cobertura runtime, so Cobertura and its dependencies
> =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 must be on your classpath.
> =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 -->
> =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 <classpath refid=3D"cobertura.classpath=
" />
>
> =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 <!--
> =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 Generete the XML report for=
 merging with CruiseControl log.
> =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 -->
> =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 <formatter type=3D"xml" />
> =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 <batchtest todir=3D"${reports.xml.dir}">
> =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 <fileset dir=3D"${testsrc.d=
ir}">
> =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 <include name=
=3D"**/*TestSuite.java" />
> =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 </fileset>
> =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 </batchtest>
> =A0=A0=A0=A0=A0=A0=A0 </junit>
>
> ******************************************************************
> David Saff escribi=F3:
>
> Tavo,
>
> How are you running the tests?
>
>    David Saff
>
> On Thu, Sep 24, 2009 at 4:36 PM, Tavo <[email protected]> wrote:
>
>
> Hi
>
> =A0 =A0 =A0 After executing test based on TestSuites, the report detail s=
hows
> 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().
>
> =A0 =A0 =A0 We need to customize the reports generated by junit, so it can
> show the actual test class, instead (or besides) the testsuite class.
>
> =A0 =A0Any advice will be much appreciated.
>
> Thanks,
> Tavo.
>
> -------------------------------------------------------------------------=
-----
> Come build with us! The BlackBerry&reg; 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&#45;12, 2009. Register now&#3=
3;
> http://p.sf.net/sfu/devconf
> _______________________________________________
> Junit-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/junit-devel
>
>
>
> __________ Information from ESET Smart Security, version of virus signatu=
re
> database 4536 (20091023) __________
>
> The message was checked by ESET Smart Security.
>
> http://www.eset.com
>
>
>
>
>
>
> __________ Information from ESET Smart Security, version of virus signatu=
re
> database 4536 (20091023) __________
>
> The message was checked by ESET Smart Security.
>
> http://www.eset.com
>

---------------------------------------------------------------------------=
---
Come build with us! The BlackBerry(R) 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/devconference