Do you mean unit testing with frameworks like NUnit, of simply unit test = testing the functionalities of function one-by-one?
Unit testings with NUnit and other stuffs needs a lot of code. It's efficient, but add +50% to the development time (or costs). This is somethint that is hard to achieve if you do custom software development...
Mostly simple unit tests and proper logging is how testing/debugging works...
NUnit like unit testing are rarely used in the .NET (at least i've never met a software company around where it's done). It's almost inpossible even to convince your employees to invest some $ for researching/learn the usage of usefull frameworks - they (who're sitting up in the big chairs) wan't profit imediately...
So i'm sick of this approaches, and will switch my employee soon - i've finally found one, where it's possible to play around with new frameworks, to teach the basics of it and to make a standard from them for a newly recruited .net team
You must be kidding, right? I mean, all the buzz in the community about testing and even microsoft adding more TDD suppor to VisualStudio should be a sign that there are a lot of writing unit test, is it not?
Without unit testing it will be bugging and debugging instead of coding and debugging
"Silence will create respect and dignity; justice and fair play will bring more friends;
benevolence and charity will enhance prestige and position; courtesy will draw benevolence;
service of mankind will secure leadership and good words will overcome powerful enemies"
Ali (Peace be upon him)