Return-Path: 
 <camel-dev-return-5326-apmail-activemq-camel-dev-archive=activemq.apache.org@activemq.apache.org>
Delivered-To: apmail-activemq-camel-dev-archive@locus.apache.org
Received: (qmail 40937 invoked from network); 22 Aug 2008 15:56:34 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2)
  by minotaur.apache.org with SMTP; 22 Aug 2008 15:56:34 -0000
Received: (qmail 52225 invoked by uid 500); 22 Aug 2008 15:56:32 -0000
Delivered-To: apmail-activemq-camel-dev-archive@activemq.apache.org
Received: (qmail 52210 invoked by uid 500); 22 Aug 2008 15:56:32 -0000
Mailing-List: contact camel-dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:camel-dev-help@activemq.apache.org>
List-Unsubscribe: <mailto:camel-dev-unsubscribe@activemq.apache.org>
List-Post: <mailto:camel-dev@activemq.apache.org>
List-Id: <camel-dev.activemq.apache.org>
Reply-To: camel-dev@activemq.apache.org
Delivered-To: mailing list camel-dev@activemq.apache.org
Received: (qmail 52199 invoked by uid 99); 22 Aug 2008 15:56:32 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 22 Aug 2008 08:56:32 -0700
X-ASF-Spam-Status: No, hits=-0.0 required=10.0
	tests=SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (athena.apache.org: local policy)
Received: from [195.69.129.178] (HELO exsmtp02.exserver.dk) (195.69.129.178)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 22 Aug 2008 15:55:33 +0000
Received: from EXVS04.exserver.dk ([10.10.10.84]) by exsmtp02.exserver.dk with
 Microsoft SMTPSVC(6.0.3790.1830);
	 Fri, 22 Aug 2008 17:53:56 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [SPAM]  Re: code coverage reports - cobertura or clover
Date: Fri, 22 Aug 2008 17:53:41 +0200
Message-ID: <4C1FB9C00D24A140906239533638C4D2051C6629@EXVS04.exserver.dk>
In-Reply-To: <ec6e67fd0808220842gc4a4677q6bc9f4e83387040d@mail.gmail.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [SPAM]  Re: code coverage reports - cobertura or clover
Thread-Index: AckEbXtKGIrcvkQmQw6K7ijqNXrQFwAAQtEg
From: "Claus Ibsen" <ci@silverbullet.dk>
To: <camel-dev@activemq.apache.org>
X-OriginalArrivalTime: 22 Aug 2008 15:53:56.0526 (UTC)
 FILETIME=[48C104E0:01C9046F]
X-Virus-Checked: Checked by ClamAV on apache.org

2 years ago I did some hacking on webwork/xwork to get the clover =
working.
But it was ANT based. But here are a few snippets might come handy.

It was capable of skipping isLogDebug statements. Anyway I guess we have =
some cobertura bits in our pom.xml that is useable.



Finding some snippets now:
  <plugin>
                <groupId>org.apache.maven.plugins</groupId>
                <artifactId>maven-clover-plugin</artifactId>
                <configuration>
                    <jdk>1.5</jdk>
                    =
<licenseLocation>lib/bootstrap/clover.license</licenseLocation>
                </configuration>
            </plugin>


<target name=3D"clover.report" depends=3D"test" description=3D"generate =
coverage reports" unless=3D"skip.tests">
        <clover-report>
            <current outfile=3D"${dist.docs}/clover">
                <format type=3D"html" =
filter=3D"logDebug,logIsDebugEnabled"/>
            </current>
        </clover-report>
        <clover-log filter=3D"logDebug,logIsDebugEnabled"/>
    </target>

    <target name=3D"clover.historical" depends=3D"clover.report" =
description=3D"generate coverage historical reports"
            unless=3D"skip.tests">
        <clover-historypoint historyDir=3D"${build.clover}"/>

        <clover-report>
            <historical outfile=3D"${dist.docs}/clover" =
historyDir=3D"${build.clover}">
                <format type=3D"html" =
filter=3D"logDebug,logIsDebugEnabled"/>
            </historical>
        </clover-report>
        <clover-log filter=3D"logDebug,logIsDebugEnabled"/>
    </target>

        <mkdir dir=3D"${build.clover}"/>
        <clover-setup initString=3D"${build.clover}/coverage.db">
            <statementContext name=3D"logIsDebugEnabled" =
regexp=3D"[\s]*if[\s]*\([\s]*(log|_log|LOG|_LOG)\.isDebugEnabled.*"/>
            <statementContext name=3D"logDebug" =
regexp=3D"[\s]*(log|_log|LOG|_LOG)\.debug[\s]*\(.*"/>
            <files>
                <exclude name=3D"${src.test}/**/*.java"/>
            </files>
        </clover-setup>


Med venlig hilsen
=20
Claus Ibsen
......................................
Silverbullet
Skovsg=E5rdsv=E6nget 21
8362 H=F8rning
Tlf. +45 2962 7576
Web: www.silverbullet.dk

-----Original Message-----
From: James Strachan [mailto:james.strachan@gmail.com]=20
Sent: 22. august 2008 17:42
To: camel-dev@activemq.apache.org
Subject: [SPAM] Re: code coverage reports - cobertura or clover

2008/8/22 Claus Ibsen <ci@silverbullet.dk>:
> Hi
>
> I was wondering if it was possible to setup the CI server to once a =
week or so to run unit test with coverage enabled.
>
> I would love to have this auto generated once in a while to find gaps =
in our testing and where we could improve or even prepare for =
@deprecated obsolete code.
>
> I have run the reports locally myself some times but I tend to be busy =
with all kind of other tickets and wiki documentation that my poor =
laptop can't run longer unit tests at the same time ;)

Great idea!

If someone can hack the build to actually run the code coverage
reports, I can setup a nightly build to upload it to Apache.

Am thinking we keep the nightly distro running, whether tests pass or
not - then have a nightly 'site' build which runs all the tests and
includes code coverage?

--=20
James
-------
http://macstrac.blogspot.com/

Open Source Integration
http://open.iona.com