Comments on: Most Programmers Don’t Write Tests http://stuffthathappens.com/blog/2007/09/27/most-programmers-dont-write-tests/ Technology and Geek Stuff by Eric Burke Mon, 26 Jul 2010 14:36:32 -0400 http://wordpress.org/?v=2.8.6 hourly 1 By: Matt Taylor http://stuffthathappens.com/blog/2007/09/27/most-programmers-dont-write-tests/comment-page-1/#comment-197 Matt Taylor Sat, 06 Oct 2007 12:15:39 +0000 http://stuffthathappens.com/blog/2007/09/27/most-programmers-dont-write-tests/#comment-197 1. Yes 2. Currently, 1/4 devs on my team are as dedicated to test-first-development as I am. 3. Yes, I do. Of all the places I've worked, my current environment is just about 'average' when it comes to testing. 1. Yes
2. Currently, 1/4 devs on my team are as dedicated to test-first-development as I am.
3. Yes, I do. Of all the places I’ve worked, my current environment is just about ‘average’ when it comes to testing.

]]> By: prashant http://stuffthathappens.com/blog/2007/09/27/most-programmers-dont-write-tests/comment-page-1/#comment-144 prashant Tue, 02 Oct 2007 09:23:16 +0000 http://stuffthathappens.com/blog/2007/09/27/most-programmers-dont-write-tests/#comment-144 1.Rarely.Sorry for this.Will try to improve from now onwards. 2.People who are in core business functions team write quite often.People like me in web development rarely write in our project.So can say 20%.Now from refactored code base things started improving. 3.Unfortunately not. 1.Rarely.Sorry for this.Will try to improve from now onwards.
2.People who are in core business functions team write quite often.People like me in web development rarely write in our project.So can say 20%.Now from refactored code base things started improving.
3.Unfortunately not.

]]> By: Ronald http://stuffthathappens.com/blog/2007/09/27/most-programmers-dont-write-tests/comment-page-1/#comment-136 Ronald Mon, 01 Oct 2007 09:51:05 +0000 http://stuffthathappens.com/blog/2007/09/27/most-programmers-dont-write-tests/#comment-136 1. Yes 2. 80% (working on it) 3. unfortunately not, but it's something we are aware of and working towards. 1. Yes
2. 80% (working on it)
3. unfortunately not, but it’s something we are aware of and working towards.

]]> By: Robert http://stuffthathappens.com/blog/2007/09/27/most-programmers-dont-write-tests/comment-page-1/#comment-110 Robert Sat, 29 Sep 2007 01:34:24 +0000 http://stuffthathappens.com/blog/2007/09/27/most-programmers-dont-write-tests/#comment-110 I think the culture of the language needs to promote testing. The Perl community has done so in recent years and now testing is part of the culture and a really big deal. I think the culture of the language needs to promote testing. The Perl community has done so in recent years and now testing is part of the culture and a really big deal.

]]> By: Aaron Saray http://stuffthathappens.com/blog/2007/09/27/most-programmers-dont-write-tests/comment-page-1/#comment-109 Aaron Saray Sat, 29 Sep 2007 00:36:23 +0000 http://stuffthathappens.com/blog/2007/09/27/most-programmers-dont-write-tests/#comment-109 There's a distinction here to be made - those who write tests who are in control of their development time and strategies, and those who write tests - or don't - who aren't in control of their development strategies. Whether its a department philosophy or an analyst philosophy to write tests/ not write tests, determines a lot of times in larger coding shops whether tests will be created. I work on a lot of legacy code that isn't very conducive to writing test cases - that is to say... I haven't found an easy way to write tests around it that don't modify the existing code. With a leadership base that does not support a test based development paradigm, building such as system is nearly impossible... but I don't think that should reflect on me. The reason I bring this up is, although these answers may be accurate and truthful for the developer answering, are they affected/manipulated by outside authorities? -aaron There’s a distinction here to be made – those who write tests who are in control of their development time and strategies, and those who write tests – or don’t – who aren’t in control of their development strategies. Whether its a department philosophy or an analyst philosophy to write tests/ not write tests, determines a lot of times in larger coding shops whether tests will be created.

I work on a lot of legacy code that isn’t very conducive to writing test cases – that is to say… I haven’t found an easy way to write tests around it that don’t modify the existing code. With a leadership base that does not support a test based development paradigm, building such as system is nearly impossible… but I don’t think that should reflect on me.

The reason I bring this up is, although these answers may be accurate and truthful for the developer answering, are they affected/manipulated by outside authorities?
-aaron

]]> By: JR http://stuffthathappens.com/blog/2007/09/27/most-programmers-dont-write-tests/comment-page-1/#comment-108 JR Fri, 28 Sep 2007 19:38:16 +0000 http://stuffthathappens.com/blog/2007/09/27/most-programmers-dont-write-tests/#comment-108 1. Yes 2. None at my current place of employment. 3. I hope not. One thing I've noticed at my current job and some of my past ones are not a lot of developers are taking the time to structure their code to be tested. The current code base I inherited is littered with direct JDBC calls, making it impossible to test. 1. Yes
2. None at my current place of employment.
3. I hope not.

One thing I’ve noticed at my current job and some of my past ones are not a lot of developers are taking the time to structure their code to be tested. The current code base I inherited is littered with direct JDBC calls, making it impossible to test.

]]> By: Pete McKinstry http://stuffthathappens.com/blog/2007/09/27/most-programmers-dont-write-tests/comment-page-1/#comment-106 Pete McKinstry Fri, 28 Sep 2007 18:32:54 +0000 http://stuffthathappens.com/blog/2007/09/27/most-programmers-dont-write-tests/#comment-106 1. Yes 2. 5-10% 3. Yes, probably typical. 1. Yes
2. 5-10%
3. Yes, probably typical.

]]> By: Dennis S http://stuffthathappens.com/blog/2007/09/27/most-programmers-dont-write-tests/comment-page-1/#comment-102 Dennis S Fri, 28 Sep 2007 16:25:11 +0000 http://stuffthathappens.com/blog/2007/09/27/most-programmers-dont-write-tests/#comment-102 I've reread the #2 question, I guess it would be allowable to say 100% if I my colleagues write zero tests like I do... Of course, that's just my opinion, I could be wrong. (sorry Dennis Miller). Ok for real answers... 1. When I'm able to, my ability to test Swing GUI work is hampered by the framework I work within. 2. No idea. 3. More than I'd like to think. :-( I’ve reread the #2 question, I guess it would be allowable to say 100% if I my colleagues write zero tests like I do… Of course, that’s just my opinion, I could be wrong. (sorry Dennis Miller). Ok for real answers…

1. When I’m able to, my ability to test Swing GUI work is hampered by the framework I work within.
2. No idea.
3. More than I’d like to think. :-(

]]> By: Emmanuel Pirsch http://stuffthathappens.com/blog/2007/09/27/most-programmers-dont-write-tests/comment-page-1/#comment-100 Emmanuel Pirsch Fri, 28 Sep 2007 15:04:49 +0000 http://stuffthathappens.com/blog/2007/09/27/most-programmers-dont-write-tests/#comment-100 Sorry for the mising letters in my comment, my keyboard is acting up! Sorry for the mising letters in my comment, my keyboard is acting up!

]]> By: Emmanuel Pirsch http://stuffthathappens.com/blog/2007/09/27/most-programmers-dont-write-tests/comment-page-1/#comment-99 Emmanuel Pirsch Fri, 28 Sep 2007 15:03:28 +0000 http://stuffthathappens.com/blog/2007/09/27/most-programmers-dont-write-tests/#comment-99 1. Yes 2. I'd say less han 5% 3. I gess as far as automated testing is concerned, there is no typical work environment. Don't feel bad about your job, from my experience, many companies focus on defining bloated development processes but fails to use well recognized practices like automated testing and continuous integration. I found that the promotion of good development practice is a continuous effort. I think that for my part, this effor is a tax ;-) I'm willing to pay. 1. Yes
2. I’d say less han 5%
3. I gess as far as automated testing is concerned, there is no typical work environment.

Don’t feel bad about your job, from my experience, many companies focus on defining bloated development processes but fails to use well recognized practices like automated testing and continuous integration.

I found that the promotion of good development practice is a continuous effort. I think that for my part, this effor is a tax ;-) I’m willing to pay.

]]>