Tom, from my (personal?!) philosophy, tests should be with the tested targets. My experience tells me that tests get out of focus if they are in a separate tree. Now when you are going to start hacking, is your approach creating use cases, sequence diagrams etc. before, or something like class responsibility cards?
M. ----- Original Message ----- From: "Tom Drake" <[EMAIL PROTECTED]> To: "Tomcat Dev List" <[EMAIL PROTECTED]> Sent: Wednesday, November 14, 2001 8:39 PM Subject: Distributed Session Management > Tomcat Developers: > > I'm going to try to synthesize the results of yesterdays > discussion on Distributed Session Management into some > working code. From what I can tell, there will be some > changes and new objects in the org.apache.session > package, and possibly some new objects in the > org.apache.cluster package. > > I should have something to share in the next couple of > days. I'll be creating JUnit tests as I write this code. Is there > a standard place to put JUnit tests, or can I simply place > them in the same package as the classes being tested? > > Regards, > > Tom Drake > Email: [EMAIL PROTECTED] > > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
