Re: Clover Fight! :-)
Peter Donald <peter-4lf8KW9E9MLMqX/[email protected]>
| Newsgroups | gmane.comp.java.jcontainer.interest |
|---|---|
| Message-ID | <[email protected]> |
On Tue, 11 Nov 2003 02:35 am, Jason van Zyl wrote: > This is meant to be a friendly jibe :-) :) > Bob and I have been having clover fights lately as I have only really > started doing TDD in the last three weeks I guess I'm lost in the > novelty of it all. Its one of those instantaneous feedbacks that makes it feel like your making progress ;) > At any rate, I have taken Plexus from a horrible 20% coverage a couple > weeks ago to this: > > http://plexus.codehaus.org/clover/index.html > > Talking to Paul Hammant and looking at stuff like xstream and qdox > definitely lit a fire under my ass. I used to write a few tests for years but after looking at qdox I completely changed the way I did unit testing. Now most of my tests are close to the source, involve no external dependencies etc. However my strategy has generally been to migrate code out of Loom into separate toolkits and then unit test the beejesus out of that code. For example the Salt, ClassLoader, Policy, Extension etc code has all gone through this process. So it will probably take some time to get our level of unit testing up significantly unless someone else takes the initiative (which Peter seems to be doing - yea!). However I would recomend you drop some of the code in Plexus and make use of external libraries that are unit tested where possible. For example you have some code that duplicates functionality like that in Salt http://spice.sourceforge.net/salt/ which I would recomend you use - but then I am biased ;) > As noted by Paul it is much easier for others to be involved if you're > well covered and that only makes sense. But I think in our particular > case if our containers are covered I think we could more easily explore > each others code and might eventually help toward a merger of more bits > and pieces in the future. > > Clover fight! done! Just will take abit of time. Also I would also recomend you run jester as coverage does not really measure how deep the tests are. Though then again running jester over your tests can be discouraging ;) -- Cheers, Peter Donald ------------------------------------ The two secrets to success: 1- Don't tell anyone everything. ------------------------------------