[Keelgroup] RE: [PROPOSAL] Feedback on testing

[Eric Simmerman]

Here’s my +1 to Shash’s comments. Moreover, I’m a regular user and fan of Derek’s suggested code generation tool JUnitDoclet.     -eric   --__--__--   Message: 3 From: "QuikDraw" <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Subject: Re: [Keelgroup] [PROPOSAL] Feedback on testing Date: Tue, 16 Dec 2003 12:52:27 -0600 Reply-To: [EMAIL PROTECTED]   > The test piece, is essential.  Mike has gone through and put in an > impressive set of framework for unit as well as functional testing, > and I believe he has plans for expanding the functional tests even > more. But none of that is any good if we lack tests to begin with. > > I personally haven't supplied tests to speak of, so my New Year's > resolution for Keel is going to be to remedy that.  I was thinking > that we should make it a *requirement* to have included unit tests for > every new module that is checked into CVS.  I realize that it will be > a barrier for new and exciting things to be  contributed into Keel,  > but I think it will be worth it.  For UI front-ends, we should also > require minimal functional tests. > > I know everybody generally supports the idea of unit-tests, but I am > asking specifically the community about making unit-tests a pre- > condition for checkins.  An alternative might be to allow checkins, >  but not including a module in a release/download unless there are a > significant number of tests. > > In the same vein, what about minimal javadoc requirements?   I am in complete agreement with everything Shash has said. Documentation: +1 JUnit tests before checkin: +1 Functional tests before addition of new UI modules: +1 Minimal Javadoc requirements: +1   I would suggest taking a look at http://junitdoclet.org/ for a tool that might help retrofit the existing codebase with the JUnit "wiring". The tests will still have to be added but JUnitDoclet helps with most of the mundane parts.   Something will need to be developed as a checker to handle whatever is defined as "minimal" for JavaDoc. Any ideas on how to handle this?   Thanks, Derek ===================================== --- The Gunslinger [EMAIL PROTECTED]