Eric Simmerman wrote:
Here’s my +1 to Shash’s comments.That's great. As I said, any small tutorial or instructions you guys could provide as to how best to meld these tools into Keel would be most welcome. Ideally, we can stick to the same "ant -Ddeploy.name=xxx tests" command and as it does currently, go through the Junit tests and generate a test-report as well as a test-coverage report. Same with the functional tests, for which we have a separate "anteater" target. Finally we have build-tests.sh, which builds for each of the deployment types (Struts versus Cocoon, Tomcat versus JBoss, direct versus OpenJMS) and runs through the test for each deployment and consolidates comprehensive go/no-go and detailed reports. Any ideas on how best to incorporate JUnitDoclet, based on your JUnitDoclet and KJeel experience, for the least amount of obtrusiveness?
Moreover, I’m a regular user and fan of Derek’s suggested code generation tool JUnitDoclet.
-eric
Shash
PS: Will read/respond in the morning http://keelframework.org/documentation Keelgroup mailing list [EMAIL PROTECTED] http://lists.keelframework.com/listinfo.cgi/keelgroup-keelframework.com
