Scared of proper testing?

When I say testing, developers imagine an unholy staff of angry bald testers, clients imagine the cost to double and management imagine hiring twice as many employees. This is not what testing really is!

Writing code is most about solving bugs, and this is very time consuming. Testing is often confused with finding bugs but is rather ways of preventing bugs to happen. It is about not start working until your desk is clean.  It is about safety first, and solve problems now instead of leaving them for later. 

• The developer should test his own code and he should use unit testing to accomplish this. Despite what everyone thinks, unit testing is more about design than validation. Developers are forced to implement good design into the project instead of full speed, head first development that usually renders most of the bugs.
• When a testing suite is properly setup in a project the client will notice this that the amount of bugs found will be significantly reduced and the stability of the product will be increased. The cost will change, but it is hard to say if it will increase or decrease. The cost of finding and fixing bugs will be replaced with proper testing that adds to the value of the product.
• Management will have to get all tools required for proper testing. This means tools for unit testing, continuous integration and for automating testing. All of these tools are available for free or as parts in Microsoft Team Foundation Suite. It is an investment that will pay for itself over and over again.

My question to you is: How much time do you spend looking for bugs, handling bug reports, fixing bugs and releasing bug fixes?