Do you use unit tests in your ASP.NET applications?

I read a lot of programming websites. In my current job I write ASP.NET applications, so a site I read often is http://www.asp.net/. They have a poll of the week feature that asks a multiple choice question and displays the results. This week the question was “Do you use unit tests in your ASP.NET applications?” I can’t imagine writing an application of any type without unit testing. So I voted for “Yes, throughout the application:”. Since the most popular answer was “What are unit tests?:” I’ll give a brief explanation of a unit test. A unit test is testing a piece of code separate from the rest of the application. The goal is to make sure that specific part of the code functions properly. Let’s use a car as an example. One item you would want to unit test would be the steering “module”. You would do this simply by verifying that it performs as expected. If the wheels do not move when you turn the steering wheel to the right, you will need to fix that module. Hopefully this was the number one answer because developers are not familiar with the terminology. I can’t imagine building anything and not testing units as they are built or put in place. Which is why I was surprised to see the second most popular answer was “No, we're not using them:”. That would be the equivalent of writing an entire novel without reading any of the chapters until you reached the end, and then having someone read it and tell you if the novel “works”. Not an effective way to create something. The screenshot shows the poll results as of May 4, 2006 1:41pm Pacific Time.