The "test" code ought to live in the same module as the server side code, if only because the two will be inseperable. Over time, in conjunction with coverage analysis, the test hierarchy will include performance loading tests, threading tests, authentication tests, and places where the specification is in fact ambiguous as to what should be done. With all these specific parts, at best I can see that the test framework can have a portion that is intended to be "standard", and that which is specific to the Slide implementation. Maybe I'm wrong, but I don't see the sense in separation.
I'd say Stefano wanted to say the testsuite is high level and so valuable it could well be be used for other WebDAV projects as well. Tests specific to the Slide kernel should go into that Slide kernel as well...
Stefano, please correct me if I got you wrong...
Oliver
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
