Programming bugs have enormous costs: time, money, frustrations, and even lives. It is possible to lessen as much of these pains as possible by creating and continuously executing test cases for our software. In this article I will try to explain a practical and common approach to address programming defects before they make it past our local development environment. For years now, unit testing has been used by software developers as a process of verification of their programs. But there have been always some doubts in the minds of the programmers about who should write the tests.