you're reading...

NUnit rocks

NUnit kicks ass!

Compare these two scenarios

You write an extensive class library with many interdependent classes. To debug your work you write the entire application and go through everything until it works.

Problem: You make some minor modifications which cause major breaks in the code. Repeat the debugging process yet again.

You create the same library as before. But you also create a new assembly, each class in this assembly tests fixtures of the code, each method in the classes tests one ‘feature’. By using the tests you elmininate a large portion of the debugging that needs to be done.

In the next revision of your software you make some minor changes which cause major breaks in the code. Before you even think that the code you changed works, the tests show you first hand that they don’t (you can even debug those features from within the test). Because your tests break you know exactly where the problem starts occuring and can more easily find the problem.

In other news, I alerted AVG to a virus that they didn’t yet detect. Less than 24 hours later they have e-mailed me back telling me that it was I-worm/Palyh.A and that it will be detected starting with the next update.


About James

I am a Senior Developer/Consultant for InfoPlanIT, LLC. I previously spent over 7 years as a Product Manager for what eventually became ComponentOne, a division of GrapeCity. While there, I helped to create ActiveReports 7, GrapeCity ActiveAnalysis, and Data Dynamics Reports.


No comments yet.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s


%d bloggers like this: