I know this question has been asked before, but none of the existing SO questions provide an adequate answer for my particular case.
I am a lone developer working on a project mainly in my spare time. Until now, I am approaching 100 classes, and I am beginning to realize that testing many classes is becoming difficult. Especially when I go back and add operator overloading for =, <>, CTypeand Not; implement IComparable(Of T), IEquatable(Of T), IEqualityComparer(Of T); and overriding basic methods such as Equalsand GetHashCode.
My current testing method was to accidentally cross out some code Debug.Printfor a particular class / method in a fictitious form with one button, start the project, click the button and make sure that the Debug window has the expected cost. But this is tiring, and begins to become an aversion to time.
What I know, what I need to do for each class, prepare a set of tests specific to this class to test its functionality. Therefore, I move on to testing frameworks such as NUnit, Gallio / MbUnit, etc. But I really don’t see the meaning in them. It still seems that I can simply write a dedicated test class for each implemented class, wrapped in blocks #If DEBUG/#End If, and associate them with a bunch of buttons in large form to run my tests.
But it may take weeks at my current rate. Therefore, I ask that their opinion on how to approach something like this. I better understand how to integrate one of these open source testing infrastructures into my project? Or should I just write a bunch of test classes and display their data somewhere?
I use VB Express 2010 and VS 2010, depending on which computer I work on, so I will need to test in both. I am not going to convert the project to C # in the near future, so I will be grateful for the answers compatible with VB.NET.
Thank!