Ahh, don't let anyone brow-beat you into not testing as you wish. Unit testing is simply a mechanism to help improve the quality of the software you write. It's but one tool.
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. -- Brent Rector, .NET Wise Owl Demeanor for .NET - an obfuscation utility http://www.wiseowl.com/Products/Products.aspx -----Original Message----- From: Dean Cleaver [mailto:[EMAIL PROTECTED]] Sent: Wednesday, April 17, 2002 1:00 PM To: [EMAIL PROTECTED] Subject: Re: [DOTNET] .NET testing tools Yeah - fair point. I guess it was just the validate password function that got me wondering - I wanted to test my logic (given I am an ex-VB programmer, and wanted to ensure my string handling in C# was correct) but without creating these users and roles for the thread context etc such that the functions would pass the declarative security and all the internal checks I couldn't get to the password validation functions... So I guess what I wanted isn't really unit testing at all, but just a functional check of one section for my own sanity... Dino You can read messages from the DOTNET archive, unsubscribe from DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.
