Testing....


I've officially shaved my head and drank the kool aid! Testing my code with a testing framework has become a valuable part in my development life cycle. I have had to adapt a few caveats to make testing work for my job. For example, I do some small applications that only live for a few months and don't futs with the core of the business data so I typically won't spend time writ ting tests for those. For the larger applications, lifespan of over a year and if they touch business critical data, I've made a point of putting in tests. I haven't seen the giant payoffs yet but I'm hoping soon I'll have one of those moments where I'll realize i just saved the company $XXXXX.

Right now i can see the value in writ ting tests and have been putting them in a practice to hopefully form a good habit but still have a lot of questions about testing in general. What to test, how many tests to write, what not to test, should i use NUnit or MSTest, how to test effectively (only for true and false, for exceptions, etc...). I'm sure it will all come in good time and I'm prepared to keep plugging away until it does.

Thanks Tim Barcz and Chris Sutton for showing me the light!