hi, some more unit tests have been added to JAMES-427.
as suggested, i looked into the pre-v2and3-merger-trunk tag. the tests contained in there were run in a stand-alone app against a full-fledged James instance. what we have now is a much more lightweight approach with very short turn-around cycles. it turns out to be real fun and i can only recommend to others adding more tests :-)
even though some tested units depend on a little bit too much other objects they want to have injected beforehand.
nevertheless, i got some hints from the pre-v2and3 stuff on possible future tests.
a specific class from this set was named "POP3Hammering" to reproduce a certain "stuck file" issue under windows. is this still relevant?
from the way how i read it, the pre-v2and3 suite was also intended to be a stress/load testing utility. this is different from unit testing. i will start working in this area soon.
a rather nasty thing i discovered was that RemoteManagerHandler makes the optimistic assumption that the UsersRepository he accesses holds JamesUser instances, while the repository's interface contract only assures to return User instances. it's not really a bug, since it obviously works, but it hinders somewhat exchanging the underlying implementation ;-)
bernd --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
