Over lunch I hooked up clover to Keel, it was surprisingly easy. Once I get a chance to enter some tracker-items, I'll check the changes in to the build.xml. There is one property in ant.properties that needs to be uncommented to enable clover instrumentation. Then clean, assemble-deploy, tests, clover.html/clover.pdf. In addition, you need to have clover.jar int $ANT_HOME/lib and keel-server/lib (I'll change this to be a test-tool lib dir under keel-build, since I'm sure other tools will need JARs only during testing).
In any case, see attached summary PDF. Looks like we have just under 20% test coverage :-(. For some classes, even though we don't have direct tests, they get covered somewhat because of indirect refrences to the container and dependencies on other services. Shash
clover-report-current.pdf
Description: Adobe PDF document
