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 -----Original Message----- From: dotnet discussion [mailto:[EMAIL PROTECTED]] On Behalf Of Brad Wilson Sent: Thursday, 18 April 2002 07:49 To: [EMAIL PROTECTED] Subject: Re: [DOTNET] .NET testing tools Yes, but this isn't how it gets used in the real world. Doesn't it worry you to create these tests that don't accurately simulate what _really_ happens? Sometimes (many times?) bugs are interplay between two components. --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.350 / Virus Database: 196 - Release Date: 17/04/2002 You can read messages from the DOTNET archive, unsubscribe from DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.
