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]
