Comments on: To test or not to test http://www.woloszyn.org/2007/12/09/to-test-or-not-to-test/ Mumbling about software Sat, 04 Feb 2012 23:39:55 +0000 http://wordpress.org/?v=2.3.1 By: znachor http://www.woloszyn.org/2007/12/09/to-test-or-not-to-test/#comment-71 znachor Mon, 07 Jan 2008 11:08:39 +0000 http://www.woloszyn.org/2007/12/09/to-test-or-not-to-test/#comment-71 Related article from InfoQ: Private Methods, Test Driven Development, and Good Design: http://www.infoq.com/news/2008/01/private-methods-tdd-design Related article from InfoQ: Private Methods, Test Driven Development, and Good Design: http://www.infoq.com/news/2008/01/private-methods-tdd-design

]]> By: znachor http://www.woloszyn.org/2007/12/09/to-test-or-not-to-test/#comment-9 znachor Mon, 10 Dec 2007 13:27:51 +0000 http://www.woloszyn.org/2007/12/09/to-test-or-not-to-test/#comment-9 Valid points. Looks like going towards testing public interface is a way forward. However I still have this thought that if we do that that we loose the benefit of test-first approach when we create an unit which is not a part of public interface. As side note there is pretty interesting debate on InfoQ about Dependency Injection: http://www.infoq.com/news/2007/12/does-di-pay-off Valid points. Looks like going towards testing public interface is a way forward. However I still have this thought that if we do that that we loose the benefit of test-first approach when we create an unit which is not a part of public interface.

As side note there is pretty interesting debate on InfoQ about Dependency Injection: http://www.infoq.com/news/2007/12/does-di-pay-off

]]> By: Adrian http://www.woloszyn.org/2007/12/09/to-test-or-not-to-test/#comment-8 Adrian Mon, 10 Dec 2007 12:21:53 +0000 http://www.woloszyn.org/2007/12/09/to-test-or-not-to-test/#comment-8 I think that unit test (certainly inn TDD) should only test the behaviour of the class, i.e. the public or maybe protected methods. You should find that any private methods are implicitly tested anyway, particularly if you're using TDD. One irritation I do find however is that, when using Spring, I have to sometimes create protected setter methods to allow the unit tests to inject dependencies or provide mock behaviour. Probably something I'm doing wrong...... I think that unit test (certainly inn TDD) should only test the behaviour of the class, i.e. the public or maybe protected methods. You should find that any private methods are implicitly tested anyway, particularly if you’re using TDD.

One irritation I do find however is that, when using Spring, I have to sometimes create protected setter methods to allow the unit tests to inject dependencies or provide mock behaviour.

Probably something I’m doing wrong……

]]>