Comments on: Testing Your Code to Test Yourself http://lostechies.com/chrismissal/2009/01/15/testing-your-code-to-test-yourself/ Thoughts while working and playing as a Software Developer Thu, 11 Apr 2013 16:53:00 +0000 hourly 1 http://wordpress.org/?v=3.4.2 By: Serhat Özgel http://lostechies.com/chrismissal/2009/01/15/testing-your-code-to-test-yourself/#comment-12 Serhat Özgel Fri, 13 Feb 2009 14:00:32 +0000 /blogs/chrismissal/archive/2009/01/15/testing-your-code-to-test-yourself.aspx#comment-12 Misko Hevery actually has more than one good presentations about the topic. Search for "clean code talks" on youtube. Misko Hevery actually has more than one good presentations about the topic. Search for “clean code talks” on youtube.

]]> By: Mihai Mahulea http://lostechies.com/chrismissal/2009/01/15/testing-your-code-to-test-yourself/#comment-11 Mihai Mahulea Tue, 27 Jan 2009 08:59:25 +0000 /blogs/chrismissal/archive/2009/01/15/testing-your-code-to-test-yourself.aspx#comment-11 Very good post. From my experience I think there should be a clear difference between TDD and unit testing. Writing all test sometime after a good amount of code piles up isn't a great idea. Very good post.

From my experience I think there should be a clear difference between TDD and unit testing.
Writing all test sometime after a good amount of code piles up isn’t a great idea.

]]> By: Chris Missal http://lostechies.com/chrismissal/2009/01/15/testing-your-code-to-test-yourself/#comment-10 Chris Missal Mon, 26 Jan 2009 21:01:15 +0000 /blogs/chrismissal/archive/2009/01/15/testing-your-code-to-test-yourself.aspx#comment-10 To name a few: classes that do too much, "new" operators inside constructors, static methods that do work, classes that rely on unavailable concrete services (not abstractions of these services), etc. To name a few: classes that do too much, “new” operators inside constructors, static methods that do work, classes that rely on unavailable concrete services (not abstractions of these services), etc.

]]> By: Michael Bolton http://lostechies.com/chrismissal/2009/01/15/testing-your-code-to-test-yourself/#comment-9 Michael Bolton Mon, 26 Jan 2009 20:50:27 +0000 /blogs/chrismissal/archive/2009/01/15/testing-your-code-to-test-yourself.aspx#comment-9 <i>Maybe I should have been more specific in saying "easily testable" code. I think code can have working unit tests, but can still be considered "untestable".</i> What do you consider "untestable"? ---Michael B. Maybe I should have been more specific in saying “easily testable” code. I think code can have working unit tests, but can still be considered “untestable”.

What do you consider “untestable”?

—Michael B.

]]> By: Chris Missal http://lostechies.com/chrismissal/2009/01/15/testing-your-code-to-test-yourself/#comment-8 Chris Missal Thu, 15 Jan 2009 15:39:29 +0000 /blogs/chrismissal/archive/2009/01/15/testing-your-code-to-test-yourself.aspx#comment-8 @mbratton Maybe I should have been more specific in saying "easily testable" code. I think code can have working unit tests, but can still be considered "untestable". @mbratton

Maybe I should have been more specific in saying “easily testable” code. I think code can have working unit tests, but can still be considered “untestable”.

]]> By: mbratton http://lostechies.com/chrismissal/2009/01/15/testing-your-code-to-test-yourself/#comment-7 mbratton Thu, 15 Jan 2009 15:13:00 +0000 /blogs/chrismissal/archive/2009/01/15/testing-your-code-to-test-yourself.aspx#comment-7 I've seen some really bad code (with some really bad unit tests as well) I’ve seen some really bad code (with some really bad unit tests as well)

]]>