If you've got something complex enough to test in isolation, maybe you should consider it a unit in its own right? In fact the phrase "test it thoroughly in isolation" surely is what unit testing is all about? :)
What you're doing there is unit testing, but you've got one unit wrapped in another. G. -- Graeme Foster ([EMAIL PROTECTED]) Principal Software Engineer Aston Broadcast Systems Ltd. (http://www.aston.tv) Disclaimer: I really don't have a clue what I'm on about. -----Original Message----- From: dotnet discussion [mailto:[EMAIL PROTECTED]]On Behalf Of Brent E. Rector Sent: 17 April 2002 21:08 To: [EMAIL PROTECTED] Subject: Re: .NET testing tools Anytime I've a method that's reasonably complex, I like to test it thoroughly in isolation while my understanding of it is fresh and in depth. I'm not one to wait until I've an entire "unit" (whatever that might be) of code built then test it all at once. You can read messages from the DOTNET archive, unsubscribe from DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.
