Hi Nick,
You don't see the value because we're still missing the important bit which is to automatically fail the build when the coverage percentage is below a threshold. We'll get there one day :-
OTOH, I use Clover from time to time to tell me where tests should be
written. I don't look often but I like to have it when I need it.
I also use the clover reports from time to time... but they should be optional in the build process. I actually believe they are *optional*, and we have a flag (clover.enable) to enable it. Doesn't that flag work?
I do agree we could possibly do without the web reports. However, that only costs some space on the web server. I'd be okay to remove the clover reports from the zip distribution though because they're taking so much space.
+1. We could actually hardwire the link in the docs to the online version, to avoid a broken link in the local docs.
WRT the license we have a license for Cactus and I can send you the
clover jar for Cactus if you wish.
Yeah. When I started working on Cactus, I simply dropped the Clover guys a mail [1], and told them I was committer on the project (with something like a link to the contributors page as proof). I got back a link for downloading a team licenced version in (almost) no time. I guess we could just forward that link to you privately.
-chris
[1] I see they now have a form for the process:
http://www.thecortex.net/clover/freelicense.jspThanks -Vincent
-----Original Message----- From: Nicholas Lesiecki [mailto:[EMAIL PROTECTED] Sent: 25 September 2003 08:30 To: Cactus Developers List Subject: Clover?
As you all know, I am a big proponent of advanced testing techniques. (Heh, I guess anyone following this list probably is.) So, on the whole, I
like
the idea of Clover. However, I'd like to raise the question of whether
we
think it's providing enough benefit to the development effort to
justify
its continued existence in our build process. (Much in the spirit of Chris questioning AspectJ's contribution to the project.)
Do we look at the clover reports often? Do our users use them? Do they help us increase our code coverage? Or are we ignoring them? I ask because
I
don't have a clear idea of the benefits, only of the cost, which is
the
frustration of trying to turn the dratted thing off in the build
script.
(Why am I trying to turn it off?--Because I don't have a
license...another
problem though you all may have a good solution to it.) Clover also
adds
to the build's general complexity.
So what do the developers think? Is it pulling its weight?
Cheers, Nick
P.S. I won't argue with the conclusions, I just want to raise the question.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
