Man, I go on vacation for 6 days and you guys send me like 500 emails on james-dev. :)
I agree with Harmeet that more testing is better, and I agree with Peter that this isn't the place for it. I would +1 adding the testing code immediately where Harmeet left it and +++1 a task for someone to build a series testing architecture, and in doing that move this code to that separate directory and build task. I propose we build a separate directory (test/ next to src/) that holds JUnit and other tests that can verify individual components, the entire application, the default conf file, and whatever else. Each of us should be able to run a script that does a clean build to make sure what we check into CVS doesn't break anything. I know it's the ideal and we're a long way from that, but the code could really use it. I would recommend creating this in a separate directory rather than branch or tree (since we want to keep this in CVS tree) and not in the proposals directory since testing should be core and always available. Serge Knystautas Loki Technologies - Unstoppable Websites http://www.lokitech.com/ ----- Original Message ----- From: "Harmeet Bedi" <[EMAIL PROTECTED]> To: "James Developers List" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> Sent: Saturday, October 12, 2002 7:27 PM Subject: Re: cvs commit: jakarta-james/src/java/org/apache/james/testing BaseTest.java Main.java POP3Test.java TestMethod.java runtest.bat runtest.sh testconf.xml > From: "Peter M. Goldstein" <[EMAIL PROTECTED]> > > Please delete and move the code to a more appropriate set of > > directories. > > Can you suggest where ? -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
