Comments on: Some thoughts on unit tests http://andrewmccall.com/2009/07/some-thoughts-on-unit-tests/ If you want to know what I think... Tue, 02 Mar 2010 12:33:07 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: stack http://andrewmccall.com/2009/07/some-thoughts-on-unit-tests/comment-page-1/#comment-93 stack Sat, 17 Oct 2009 00:33:24 +0000 http://andrewmccall.com/?p=417#comment-93 Andrew: You mentioned making up mock objects for hbase. Can I see what you did? Trying to make the hbase tests run faster overall... Thanks. St.Ack Andrew: You mentioned making up mock objects for hbase. Can I see what you did? Trying to make the hbase tests run faster overall… Thanks. St.Ack

]]> By: John Hunsley http://andrewmccall.com/2009/07/some-thoughts-on-unit-tests/comment-page-1/#comment-67 John Hunsley Thu, 09 Jul 2009 18:57:31 +0000 http://andrewmccall.com/?p=417#comment-67 Some rules I apply when writing unit test -<br><br>1. Never write tests which rely on a resource outside of the code you're testing. i.e. Make mock objects for DAO's and stubs for external resources such as a web service end point.<br><br>2. Only test business logic. There's no point writing a test case which tests getters and setters, as you've said, and no point testing that framework you are using does the job it is supposed to do, that should be tested within that framework project itself. Some rules I apply when writing unit test -

1. Never write tests which rely on a resource outside of the code you're testing. i.e. Make mock objects for DAO's and stubs for external resources such as a web service end point.

2. Only test business logic. There's no point writing a test case which tests getters and setters, as you've said, and no point testing that framework you are using does the job it is supposed to do, that should be tested within that framework project itself.

]]>