 <p>You don't even need to discuss it with management (though the situation you describe about it is far from ideal). It's like Design by Contract - I introduced it in previous code I worked in, just as part of the development process. Once it's in, and it works, trust me, noone will dare to remove it.</p> <p>Unit testing can also be seen as a <em>part</em> of development. Hence, if you have "20 days" for developing features A, B and C, you can typically include unit tests in your estimations for development itself.</p> <p>Making unit tests is surprisingly easy. Compared with multithreading problems or any sort of complex design, unit testing is very easy to grasp for any competent developer.</p> <p>You can read good literature about it (you have dozens of tutorials online) in, say, half a day, and start doing your first tests in the afternoon.</p> <p>Really - <strong>just do it!</strong></p>