Comments on: 6 Reasons to develop your tests first http://www.lispcast.com/wordpress/2008/01/6-reasons-to-develop-your-tests-first/ Tue, 18 Nov 2008 15:30:06 +0000 http://wordpress.org/?v=2.3.1 By: Knuth e Testes » LSDR.net http://www.lispcast.com/wordpress/2008/01/6-reasons-to-develop-your-tests-first/#comment-829 Knuth e Testes » LSDR.net Mon, 28 Apr 2008 23:44:22 +0000 http://www.lispcast.com/wordpress/2008/01/6-reasons-to-develop-your-tests-first/#comment-829 [...] eu penso em TDD, escrever testes antes do desenvolvimento e tudo mais, não penso somente em ter uma ferramenta de compliance, teste puro [...] […] eu penso em TDD, escrever testes antes do desenvolvimento e tudo mais, não penso somente em ter uma ferramenta de compliance, teste puro […]

]]> By: Bysshent http://www.lispcast.com/wordpress/2008/01/6-reasons-to-develop-your-tests-first/#comment-819 Bysshent Mon, 24 Mar 2008 06:30:31 +0000 http://www.lispcast.com/wordpress/2008/01/6-reasons-to-develop-your-tests-first/#comment-819 thank you, dude thank you, dude

]]> By: Robert Synnott http://www.lispcast.com/wordpress/2008/01/6-reasons-to-develop-your-tests-first/#comment-777 Robert Synnott Mon, 11 Feb 2008 13:52:36 +0000 http://www.lispcast.com/wordpress/2008/01/6-reasons-to-develop-your-tests-first/#comment-777 I must say, I've never been convinced about test-driven development, but I do love the pictures! I must say, I’ve never been convinced about test-driven development, but I do love the pictures!

]]> By: Juvileu http://www.lispcast.com/wordpress/2008/01/6-reasons-to-develop-your-tests-first/#comment-759 Juvileu Fri, 25 Jan 2008 10:53:37 +0000 http://www.lispcast.com/wordpress/2008/01/6-reasons-to-develop-your-tests-first/#comment-759 Eu sou brasileiro Eu vo na padaria comprar pão! Translate: I'm brazilian Thanks it really have change my life! Eu sou brasileiro
Eu vo na padaria comprar pão!

Translate:

I’m brazilian
Thanks it really have change my life!

]]> By: Andy Johnson http://www.lispcast.com/wordpress/2008/01/6-reasons-to-develop-your-tests-first/#comment-757 Andy Johnson Thu, 24 Jan 2008 08:56:12 +0000 http://www.lispcast.com/wordpress/2008/01/6-reasons-to-develop-your-tests-first/#comment-757 How is it possible to do top down design with functional/object decomposition using TDD? Theoretically the first test you write would be the last one that passes. You would have to write a series of tests each testing lower functionality before hitting the bottom and then start implementing. BTW I am test infected, just playing devil's advocate here. How is it possible to do top down design with functional/object decomposition using TDD?

Theoretically the first test you write would be the last one that passes. You would have to write a series of tests each testing lower functionality before hitting the bottom and then start implementing.

BTW I am test infected, just playing devil’s advocate here.

]]> By: nibrahim.net.in » Blog Archive » 6 Reasons to develop your tests first | LispCast http://www.lispcast.com/wordpress/2008/01/6-reasons-to-develop-your-tests-first/#comment-736 nibrahim.net.in » Blog Archive » 6 Reasons to develop your tests first | LispCast Wed, 16 Jan 2008 17:35:50 +0000 http://www.lispcast.com/wordpress/2008/01/6-reasons-to-develop-your-tests-first/#comment-736 [...] 6 Reasons to develop your tests first | LispCast [...] […] 6 Reasons to develop your tests first | LispCast […]

]]> By: Alex McLean » Blog Archive » Following your imagination http://www.lispcast.com/wordpress/2008/01/6-reasons-to-develop-your-tests-first/#comment-726 Alex McLean » Blog Archive » Following your imagination Mon, 14 Jan 2008 15:10:53 +0000 http://www.lispcast.com/wordpress/2008/01/6-reasons-to-develop-your-tests-first/#comment-726 [...] This entertaining article supporting test-first development has been playing on my mind. The article is beautifully written so it is easy to see the assumed context of working to deadline on well specified problems, most probably in a commercial environment. It saddens me though that we accept this implicit context across all discussion of software development practice all too easily. [...] […] This entertaining article supporting test-first development has been playing on my mind. The article is beautifully written so it is easy to see the assumed context of working to deadline on well specified problems, most probably in a commercial environment. It saddens me though that we accept this implicit context across all discussion of software development practice all too easily. […]

]]> By: Best of Feeds - 23 links - programming, music, photography, psychology, rails « // Internet Duct Tape http://www.lispcast.com/wordpress/2008/01/6-reasons-to-develop-your-tests-first/#comment-722 Best of Feeds - 23 links - programming, music, photography, psychology, rails « // Internet Duct Tape Sun, 13 Jan 2008 15:11:43 +0000 http://www.lispcast.com/wordpress/2008/01/6-reasons-to-develop-your-tests-first/#comment-722 [...] [CODE] 6 Reasons to develop your tests first [...] […] [CODE] 6 Reasons to develop your tests first […]

]]> By: (cons 'Michael 'T) http://www.lispcast.com/wordpress/2008/01/6-reasons-to-develop-your-tests-first/#comment-719 (cons 'Michael 'T) Sun, 13 Jan 2008 03:41:33 +0000 http://www.lispcast.com/wordpress/2008/01/6-reasons-to-develop-your-tests-first/#comment-719 It's not an all or nothing issue. I worked on a math module that had to check a student's answers, and we had to make sure the normalization engine didn't oversimplify. The project was done in Scheme. Anyway, we didn't start our tests until our code was mostly done. It wasn't done in an integrated way like you suggest. But it was certainly better than no testing at all. The world is full of people telling us that you have to do certain types of programming or methodologies in order to be a trustworthy programmer. But at least with this one, you can do this part way and still get part benefits. That's a good sign. It’s not an all or nothing issue. I worked on a math module that had to check a student’s answers, and we had to make sure the normalization engine didn’t oversimplify. The project was done in Scheme.

Anyway, we didn’t start our tests until our code was mostly done. It wasn’t done in an integrated way like you suggest. But it was certainly better than no testing at all.

The world is full of people telling us that you have to do certain types of programming or methodologies in order to be a trustworthy programmer. But at least with this one, you can do this part way and still get part benefits. That’s a good sign.

]]> By: dispatches from TJICistan » Blog Archive » test first, implement next http://www.lispcast.com/wordpress/2008/01/6-reasons-to-develop-your-tests-first/#comment-718 dispatches from TJICistan » Blog Archive » test first, implement next Sun, 13 Jan 2008 03:01:30 +0000 http://www.lispcast.com/wordpress/2008/01/6-reasons-to-develop-your-tests-first/#comment-718 [...] still don’t do it that way very often, but this article presents some compelling arguments for that [...] […] still don’t do it that way very often, but this article presents some compelling arguments for that […]

]]>