Touching fire

Why is it that developers know about automated testing -- how much time it can save you, how many headaces it can help prevent, etc... -- but don't practice it?

A team that WANTS to do automated testing, but just doesn't "do it", needs a automated-testing evangelist. That's a recipe for automated-tests to infiltrate the company. The evangelist will always push for it. Now that seems like common sense to most, but people that think it's common sense are either doing automated testing as a full-team of people or it's someone that can tell their developers to do automated tests in the first place.

If management doesn't buy into it right away, create a new assembly and just stick your tests in that and do them as you develop. Try to write a test before ANY CODE, regardless of deadlines. Deadlines usually aren't hit in the real world anyway -- unless you work for a company that has hit them for the past couple years.