This project is read-only.

Next version's unit testing

Topics: Developer Forum
Aug 27, 2006 at 5:59 PM
Shishir is looking into unit testing for version 1.5. I think not currently having unit tests as part of the project is a real shortcoming. Not everyone in the development group has the built in Visual Studio 2005 unit testing. Right now he is looking into MBUnit and NUnit.
Nov 5, 2006 at 11:11 PM
I think that's a great idea too.

I've used NUnit and had pretty good luck with it. Unit testing has saved me lots of time debugging.

Actually, there is a whole TestDriven.NET suite that includes NUnit, MBUnit, and NCoverExplorer. It's excellent and highly recommended.
It's free for personal use and has tight integration with Visual Studio 2005.

NCover (and the GUI NCoverExplorer) are great because they will tell you how good your unit tests are by showing you how many lines of code each test invokes (covers). Ideally your unit tests should cause each line of code to execute, and NCover will show if your unit tests are that thorough.

I could get a unit test project added to the solution if you want.


Nov 13, 2006 at 12:41 PM
Doing unit testing on a Windows Form library presents a number of difficulties because the unit tests must interact with the graphical interface.

I did a litle research and found an NUnit extension called NUnitForms that aims to make this easier.

What are the main items that need to be tested?

Nov 14, 2006 at 6:48 PM
I don’t know that I have any specific area to test. I juts think that the more we can automate the testing the better the end product will be. I agree that the visual part of the controls are very hard to automate and unfortunately because of what the controls are most of the testing would need to be visual.

I would say we automate the unit testing as much as we reasonably can and go from there. Any research/input you can give on the visual unit testing tool would be appreciated.