----- Original Message ----- From: "Serge Knystautas" <[EMAIL PROTECTED]> To: "James Developers List" <[EMAIL PROTECTED]> Sent: Wednesday, October 16, 2002 7:34 AM 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
> Nevermind... you guys got a lot done this weekend and are ahead of me on > this. Sounds great. > Hey Serge welcome back. :-) > > 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 think we are getting there. Danny's EndToEnd test integrated with build environment gives lot of good feedback. I am planning to add some tests and integrate with build as soon as I can. I was thinking a short sanity test suite, a longer regression test suite and a set of tests that mimick specific problems like memory leak or crash would be good. In the past there was talk about creating templates and running those templates as a record and replay mechanism. I was wondering what everyone thought of that. Harmeet -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
