Thanks a bunch for all the feedback and suggestions regarding this topic. Without any negative comments on this topic, I guess we all have agreed to not checkin any new modules without sufficient unit tests. We have also agreed on "minimal" Javadoc requirements, "minimal" TBD. Lets start a discussion on "minimal". I'll start a new thread for that.
As for unit tests, Clover and JUn itDoclet are now integrated into the build system. Rudimentary documentation is at <http://66.105.113.115/vqwiki-2.3.5/jsp/Wiki?TestingHOWTO>. Now, lets get some unit tests written for the existing modules :-).
As for functional tests, I have to admit I am a bit disappointed. I looked at TestMaker and the task seemed far daunting than I am willing to take on at the moment. I also looked at Solex quite a bit. However, although I could eventually get Solex to record the HTTP transactions, and define tests, I could never get Solex to declare a failure even when I was looking for stuff that was completely missing from the page. Looks like the last Solex release was a while back, and there are many open issues/questions on their tracker that have not been looked at /answered in a while. Moreover, there is no public CVS repository, and the source bundle does not actually have any source that I can tell...I couldn't debug why it wasn't working either. In short...really frustrated. My vote: AntEater...it works for the most part, and if we need to fix something source is available (bad part, no active development anymore, so we'd have to take over maintenance). Pete/Mike....this is too hard...your territory now :-)
Shash http://keelframework.org/documentation Keelgroup mailing list [EMAIL PROTECTED] http://lists.keelframework.com/listinfo.cgi/keelgroup-keelframework.com
