Comments on: Don’t write tests to test your code http://blog.paulmoser.co.uk/index.php/2008/04/22/dont-write-tests-to-test-your-code/ So much to learn but so little time Fri, 26 Dec 2008 01:15:09 +0000 http://wordpress.org/?v=2.8.4 hourly 1 By: Kekoa http://blog.paulmoser.co.uk/index.php/2008/04/22/dont-write-tests-to-test-your-code/comment-page-1/#comment-15883 Kekoa Tue, 09 Dec 2008 21:21:04 +0000 http://blog.paulmoser.co.uk/index.php/2008/04/22/dont-write-tests-to-test-your-code/#comment-15883 Although I think your point is very valid, I think some testing is better than no testing. I have seen it be very difficult to change the mindset of seasoned programmers. They just don't get TDD, and hate testing in general. Even if testing is done out of order I feel like there is some benefit, mainly that you step through your own logic twice, and have an opportunity to catch errors in your reasoning. In my experience TDD is much easier in the earlier stages, later on, you end up having to still change both your tests and code when things change. Although I think your point is very valid, I think some testing is better than no testing. I have seen it be very difficult to change the mindset of seasoned programmers. They just don’t get TDD, and hate testing in general.

Even if testing is done out of order I feel like there is some benefit, mainly that you step through your own logic twice, and have an opportunity to catch errors in your reasoning.

In my experience TDD is much easier in the earlier stages, later on, you end up having to still change both your tests and code when things change.

]]>