Comments on: Testing Times Concluded: There’s always tomorrow, isn’t there? http://www.pramatr.com/blog/2009/09/29/testing-times-concluded-theres-always-tomorrow-isnt-there/ A collection of articles from pramatr.com on technology, security, software and anything we find interesting Wed, 28 Jul 2010 12:28:21 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: Peter Mularien http://www.pramatr.com/blog/2009/09/29/testing-times-concluded-theres-always-tomorrow-isnt-there/comment-page-1/#comment-240 Peter Mularien Wed, 30 Sep 2009 21:03:35 +0000 http://pramatr.com/?p=861#comment-240 I just have to say this is an excellent series of articles. I've run into all of these at various points in my career, with projects in various states of completeness / unit-testlessness. I recently ran into a case where I was writing unit tests for code that obviously wasn't written with testability or mocking in mind. I ended up having to make some pretty significant (scary, as you note) refactors, but the end result was better OO code and had the added bonus of having real unit test coverage! I agree that the "it works, don't break it, why do we need tests" mantra is just as painful when you hear it from fellow developers and management. Any suggestions from your personal experience? Best, Peter I just have to say this is an excellent series of articles. I’ve run into all of these at various points in my career, with projects in various states of completeness / unit-testlessness. I recently ran into a case where I was writing unit tests for code that obviously wasn’t written with testability or mocking in mind. I ended up having to make some pretty significant (scary, as you note) refactors, but the end result was better OO code and had the added bonus of having real unit test coverage!

I agree that the “it works, don’t break it, why do we need tests” mantra is just as painful when you hear it from fellow developers and management. Any suggestions from your personal experience?

Best,
Peter

]]>