Comments on: It’s OK not to call them unit tests http://lizkeogh.com/2009/11/06/its-ok-not-to-call-them-unit-tests/ Software, Training, Coaching, Writing Wed, 08 Feb 2012 12:59:05 -0500 http://wordpress.org/?v=2.8.6 hourly 1 By: Scott Schulthess http://lizkeogh.com/2009/11/06/its-ok-not-to-call-them-unit-tests/comment-page-1/#comment-8060 Scott Schulthess Tue, 25 May 2010 13:06:24 +0000 http://lizkeogh.com/?p=438#comment-8060 http://www.scottschulthess.com/coding/?p=143 I wrote a response as well but yours is better and we agree - there are a lot of other reasons to write "tests" than the ones listen in the ridic. off the wall MSDN blog post http://www.scottschulthess.com/coding/?p=143

I wrote a response as well but yours is better and we agree – there are a lot of other reasons to write “tests” than the ones listen in the ridic. off the wall MSDN blog post

]]> By: OlafLewitz - A Community of Thinkers http://lizkeogh.com/2009/11/06/its-ok-not-to-call-them-unit-tests/comment-page-1/#comment-6225 OlafLewitz - A Community of Thinkers Mon, 07 Dec 2009 21:00:05 +0000 http://lizkeogh.com/?p=438#comment-6225 [...] October. She taught me how to write haiku to connect the two sides of your brain. I learned about Behaviour Driven Development from her blog and took great value from her InfoQ article, Pulling Power: A New Software Lifespan. [...] [...] October. She taught me how to write haiku to connect the two sides of your brain. I learned about Behaviour Driven Development from her blog and took great value from her InfoQ article, Pulling Power: A New Software Lifespan. [...]

]]> By: Keith Ray http://lizkeogh.com/2009/11/06/its-ok-not-to-call-them-unit-tests/comment-page-1/#comment-5881 Keith Ray Sun, 15 Nov 2009 00:36:53 +0000 http://lizkeogh.com/?p=438#comment-5881 Mike Hill and and we at Industrial Logic call the tests used in TDD "Microtests", and they are "SPIFFy": Small, Precise, Isolated, Fast, FrequentlY run. People mention the "cost" of tests in TDD, but our observation is that microtests reduce the cost of debugging far more than the tests cost in time, and they reduce the cost of regression testing. We say "isolated" but we don't mind allow other "real" collaborator objects being used in a microtest, as long as they are not awkward. We sometimes use hand-made stubs or mocks, but rarely find the need to use a mocking framework. Mike Hill and and we at Industrial Logic call the tests used in TDD “Microtests”, and they are “SPIFFy”: Small, Precise, Isolated, Fast, FrequentlY run.

People mention the “cost” of tests in TDD, but our observation is that microtests reduce the cost of debugging far more than the tests cost in time, and they reduce the cost of regression testing.

We say “isolated” but we don’t mind allow other “real” collaborator objects being used in a microtest, as long as they are not awkward. We sometimes use hand-made stubs or mocks, but rarely find the need to use a mocking framework.

]]>