Unit Testing?

[VBCrazyCoder]

Anyone do any kind of Unit Testing (testing eah function thoroughly). What is your approach, and is there any specific tools to aid in this for .NET.

Currently, I just write a Test Application, include my DLL as a reference, and then start develop cheezy forms that tests the functionality of the DLL. But I want to test more specifically and finite.

[nswan]

testing pah!!! who needs that!!!!!!??????

[nswan]

i apologise i have been drinkin!

[VBCrazyCoder]

LOL

I know alot of developers don't like to do testing, and there is usually a QA group that does that for them, but not in my case

[nswan]

when i have to do testing it involves me using values and data that i already know work! That way i don't find any bugs or have to fix anything!

All great until it gets realeased to the users! Then all hell breaks lose!

[powdir]

try NUnit http://sourceforge.net/projects/nunit . Never used it, but its based on JUnit (which i have...a little!). It's pretty handy.

I am hoping to run my latest project through NUnit ( a learning exercise ) when it's done before passing to the QA Team for formal testing so let us know how you get on.

Cheers

[shunt]

To get a good test pack together, you need to analyse the requirements of the component and based on the requirements come up with input data that:

1) Tests the components correct use
2) Tests the upper and lower limits of the component
3) Tests the component for cases where it should throw back error messages.
4) Test exceptional cases that you know usually cause problems (eg. typing non-numeric data in a numberic field, entering 0 in a field used in a calculation etc.)

At each stage, the outputs should be checked against what you expect back.

It is also helpfull to get someone else to actually do this testing, cause naturally, they don't know what will cause it to crash and therefore go crazy on the keyboard.....