Ah - ok. Is a shame - often I feel that testing the individual functions is a lot easier than testing the public interface. For example, the current project I have, I have to create a super-user, then use their user ID as authorisation to create a supervisor, and then use their ID to create a user etc...
So to test the user create function, I have to create 3 such that on creation of the last one I have someone with the right permissions to be able to create it... Whereas being able to test the several component functions of this would have been useful. Still - I think my Conditional idea will work for the few private functions I want to test. Dino -----Original Message----- From: dotnet discussion [mailto:[EMAIL PROTECTED]] On Behalf Of Brad Wilson Sent: Wednesday, 17 April 2002 23:20 To: [EMAIL PROTECTED] Subject: Re: [DOTNET] .NET testing tools Dean Cleaver wrote: > Can I ask how you use this to test "private" functions? Unit testing isn't about testing private functions. It's about testing the public interface to a component to ensure that it behaves properly in the face of valid (and invalid) input. Brad -- Read my web log at http://www.quality.nu/dotnetguy/ You can read messages from the DOTNET archive, unsubscribe from DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com. --- Incoming mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.349 / Virus Database: 195 - Release Date: 15/04/2002 --- 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.
