Comments on: "I don’t have time to test!" http://lostechies.com/joshualockwood/2009/04/13/quot-i-don-t-have-time-to-test-quot/ Just another LosTechies site Wed, 16 Feb 2011 11:54:06 +0000 hourly 1 http://wordpress.org/?v=3.4.2 By: Mark http://lostechies.com/joshualockwood/2009/04/13/quot-i-don-t-have-time-to-test-quot/#comment-109 Mark Thu, 16 Apr 2009 10:33:52 +0000 /blogs/joshua_lockwood/archive/2009/04/13/quot-i-don-t-have-time-to-test-quot.aspx#comment-109 As a new convert to tdd or at least automated testing, one of the main drawbacks was getting the framework and config write, and jumping the first hurdle or tests. But after you have done it once, even if you don't do TDD, automated testing is a god send. As a new convert to tdd or at least automated testing, one of the main drawbacks was getting the framework and config write, and jumping the first hurdle or tests.

But after you have done it once, even if you don’t do TDD, automated testing is a god send.

]]> By: Giorgio Sironi http://lostechies.com/joshualockwood/2009/04/13/quot-i-don-t-have-time-to-test-quot/#comment-108 Giorgio Sironi Thu, 16 Apr 2009 09:39:44 +0000 /blogs/joshua_lockwood/archive/2009/04/13/quot-i-don-t-have-time-to-test-quot.aspx#comment-108 Cannot agree more, small tests for domain layer code are saving my life... Cannot agree more, small tests for domain layer code are saving my life…

]]> By: Shantanu http://lostechies.com/joshualockwood/2009/04/13/quot-i-don-t-have-time-to-test-quot/#comment-107 Shantanu Thu, 16 Apr 2009 04:44:28 +0000 /blogs/joshua_lockwood/archive/2009/04/13/quot-i-don-t-have-time-to-test-quot.aspx#comment-107 As Neal Ford says, testing is only a by product of TDD. The main intention of TDD is to get your design right even before you write code. http://www.sda-india.com/conferences/2009/JAX-INDIA/slides/Neal_Ford/slides.pdf? As Neal Ford says, testing is only a by product of TDD. The main intention of TDD is to get your design right even before you write code.

http://www.sda-india.com/conferences/2009/JAX-INDIA/slides/Neal_Ford/slides.pdf?

]]> By: jlockwood http://lostechies.com/joshualockwood/2009/04/13/quot-i-don-t-have-time-to-test-quot/#comment-106 jlockwood Wed, 15 Apr 2009 22:15:32 +0000 /blogs/joshua_lockwood/archive/2009/04/13/quot-i-don-t-have-time-to-test-quot.aspx#comment-106 @Jarod Awesome reference! @Jarod Awesome reference!

]]> By: jlockwood http://lostechies.com/joshualockwood/2009/04/13/quot-i-don-t-have-time-to-test-quot/#comment-105 jlockwood Tue, 14 Apr 2009 22:06:52 +0000 /blogs/joshua_lockwood/archive/2009/04/13/quot-i-don-t-have-time-to-test-quot.aspx#comment-105 @Chris I said "complex code at the least" because if I'm truly pressed for time I have to prioritize where I spend the most testing effort. I'm currently working on a big legacy system and could probably do nothing but write tests for 2 years and not have the coverage I'd like. With this system, I tend to test the most breakable and complex pieces first (mainly so that I'm in a position to safely refactor...I'll want to simplify that code ASAP). Testing POJOs, simple DAOs and whatnot is way lower on my priority list. I tend to use TDD for new code, so it's not an issue in that respect. @Chris

I said “complex code at the least” because if I’m truly pressed for time I have to prioritize where I spend the most testing effort. I’m currently working on a big legacy system and could probably do nothing but write tests for 2 years and not have the coverage I’d like. With this system, I tend to test the most breakable and complex pieces first (mainly so that I’m in a position to safely refactor…I’ll want to simplify that code ASAP). Testing POJOs, simple DAOs and whatnot is way lower on my priority list.

I tend to use TDD for new code, so it’s not an issue in that respect.

]]> By: jlockwood http://lostechies.com/joshualockwood/2009/04/13/quot-i-don-t-have-time-to-test-quot/#comment-104 jlockwood Tue, 14 Apr 2009 21:58:35 +0000 /blogs/joshua_lockwood/archive/2009/04/13/quot-i-don-t-have-time-to-test-quot.aspx#comment-104 @Dan The key is to commit to 'wasting' a little time testing each day (commit is the key word here). As time progresses you will become more comfortable and proficient at testing. Start with simple tests using an easy-to-use test framework like NUnit. Grab a tutorial for the framework and write tests based on what you learn. Overtime you'll learn how to get more complex code under test. I'd say the key is not to get overwhelmed (if you are working on a large legacy system) and learn as you go along. If I had junit when I first started programming I'm pretty sure I would have been 'test infected' within my first year. The tools available these days are really nice. What are you doing now Dan? @Dan

The key is to commit to ‘wasting’ a little time testing each day (commit is the key word here). As time progresses you will become more comfortable and proficient at testing. Start with simple tests using an easy-to-use test framework like NUnit. Grab a tutorial for the framework and write tests based on what you learn. Overtime you’ll learn how to get more complex code under test.

I’d say the key is not to get overwhelmed (if you are working on a large legacy system) and learn as you go along. If I had junit when I first started programming I’m pretty sure I would have been ‘test infected’ within my first year. The tools available these days are really nice.

What are you doing now Dan?

]]> By: Chris Missal http://lostechies.com/joshualockwood/2009/04/13/quot-i-don-t-have-time-to-test-quot/#comment-103 Chris Missal Tue, 14 Apr 2009 20:54:49 +0000 /blogs/joshua_lockwood/archive/2009/04/13/quot-i-don-t-have-time-to-test-quot.aspx#comment-103 I like to respond to that with: "You're already testing with the debugger, TestPage1.aspx, or whatever... Just save that code and automate it!" Also, I'm going to disagree when you say "(the complex code at the least)". I find that even very simple code can benefit from tests. Small code can sometimes cause big problems when overlooked. I like to respond to that with:

“You’re already testing with the debugger, TestPage1.aspx, or whatever… Just save that code and automate it!”

Also, I’m going to disagree when you say “(the complex code at the least)”. I find that even very simple code can benefit from tests. Small code can sometimes cause big problems when overlooked.

]]> By: Jarod http://lostechies.com/joshualockwood/2009/04/13/quot-i-don-t-have-time-to-test-quot/#comment-102 Jarod Tue, 14 Apr 2009 15:53:19 +0000 /blogs/joshua_lockwood/archive/2009/04/13/quot-i-don-t-have-time-to-test-quot.aspx#comment-102 as Beck would say: the "No time for testing" death spiral. "The more stress you feel, the less testing you do. The less testing you do, the more errors you will make. The more errors you make, the more stress you feel. Rinse and repeat" http://books.google.com/books?id=gFgnde_vwMAC&pg=PA124&lpg=PA124&dq=%22no+time+for+testing+death+spiral%22&source=bl&ots=enGxrqVnuK&sig=jeFZ-rAgyVWbvdGPgXJDJvWQR-E&hl=en&ei=QrDkSYOpKJ6EtAODs6S9CQ&sa=X&oi=book_result&ct=result&resnum=1#PPA124,M1 as Beck would say: the “No time for testing” death spiral.

“The more stress you feel, the less testing you do. The less testing you do, the more errors you will make. The more errors you make, the more stress you feel.

Rinse and repeat”

http://books.google.com/books?id=gFgnde_vwMAC&pg=PA124&lpg=PA124&dq=%22no+time+for+testing+death+spiral%22&source=bl&ots=enGxrqVnuK&sig=jeFZ-rAgyVWbvdGPgXJDJvWQR-E&hl=en&ei=QrDkSYOpKJ6EtAODs6S9CQ&sa=X&oi=book_result&ct=result&resnum=1#PPA124,M1

]]> By: Dave http://lostechies.com/joshualockwood/2009/04/13/quot-i-don-t-have-time-to-test-quot/#comment-101 Dave Tue, 14 Apr 2009 14:30:51 +0000 /blogs/joshua_lockwood/archive/2009/04/13/quot-i-don-t-have-time-to-test-quot.aspx#comment-101 I've not got time to read all that! I’ve not got time to read all that!

]]> By: Jason Meridth http://lostechies.com/joshualockwood/2009/04/13/quot-i-don-t-have-time-to-test-quot/#comment-100 Jason Meridth Tue, 14 Apr 2009 14:21:36 +0000 /blogs/joshua_lockwood/archive/2009/04/13/quot-i-don-t-have-time-to-test-quot.aspx#comment-100 Here, here. Here, here.

]]>