Thank you for mentioning that stats package as a sidenote. Thinking of using it for a project now instead of analog/report magic.If you check the cactus stats (http://jakarta.apache.org/cactus/stats/index.html), you will find it is receiving quite a lot of attention (1500-2500 visits per day). It gets between 500-1500 downloads per day which is quite honorable for such a "niche" project (not only it is unit testing but only J2EE-related unit testing). Note: I don't like too much the stats from webalizer and I have started using awstats (http://jakarta.apache.org/~vmassol/awstats/awstats.jakarta.apache.org.h tml) as an experiment. Much better stats I think (except the history).
With Cactus, my impression is that a sizable number of developers know about it, are interested in it, think it is a good idea, but are too 'busy' in their day jobs to use unit testing, or more complex server-side unit testing. And for those who have pet projects, those projects are usually small enough that the benefits of setting up test cases in the mind are outweighed by adding another feature.
You mentioned later in this thread what I believe is a key point. You are doing something new and the public/users/possible committers need to learn to adopt unit testing and then 'IUT'. And while people are thinking about it, they will browse the page, and even download a copy. But until they use it for a project and see the advantages its adoption/attraction to developers may be slow. I think the documentation and polish helps find developers more than hurts, IUT is just ahead of their needs though it doesn't need to be.
It reminds me of how digital video records have been slow to take off. But their time is coming one way or another.
--
Ellis Teer
www.sitepen.com
--
To unsubscribe, e-mail: <mailto:general-unsubscribe@;jakarta.apache.org>
For additional commands, e-mail: <mailto:general-help@;jakarta.apache.org>
