Comments on: TDD as if you meant it – revisited http://gojko.net/2009/08/02/tdd-as-if-you-meant-it-revisited/ Building software that matters Thu, 02 Feb 2012 07:12:46 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: blaulabs » Blog Archive » Get your hands dirty – ein Code Retreat! http://gojko.net/2009/08/02/tdd-as-if-you-meant-it-revisited/comment-page-1/#comment-162280 blaulabs » Blog Archive » Get your hands dirty – ein Code Retreat! Tue, 25 Oct 2011 16:17:06 +0000 http://gojko.net/?p=1035#comment-162280 [...] der letzen Runde vor dem verdienten Mittagessen hat dann TDD as if you meant it uns wieder wach gemacht. Die Implementation wird erst im Test erstellt und neue Klassen/Methoden [...] [...] der letzen Runde vor dem verdienten Mittagessen hat dann TDD as if you meant it uns wieder wach gemacht. Die Implementation wird erst im Test erstellt und neue Klassen/Methoden [...]

]]> By: TDD as if you Meant It « cumulativehypotheses http://gojko.net/2009/08/02/tdd-as-if-you-meant-it-revisited/comment-page-1/#comment-149742 TDD as if you Meant It « cumulativehypotheses Tue, 30 Aug 2011 14:35:13 +0000 http://gojko.net/?p=1035#comment-149742 [...] The first outing for the exercise was at Software Craftsmanship 2009 and Gojko Adzick did an excellent writeup of that and then tried running the exercise himself [...] [...] The first outing for the exercise was at Software Craftsmanship 2009 and Gojko Adzick did an excellent writeup of that and then tried running the exercise himself [...]

]]> By: Stefan Roock http://gojko.net/2009/08/02/tdd-as-if-you-meant-it-revisited/comment-page-1/#comment-144914 Stefan Roock Sat, 30 Jul 2011 10:17:26 +0000 http://gojko.net/?p=1035#comment-144914 In my experience people often have problems understanding what exactly the rules mean and experienced TDD programmers tend to fake it - in my understanding of "TDD as if you meant it". Therefore I tried to show how it could be done, so that everybody can see the single steps: http://www.codersdojo.com/statistics/f80623b0fc6c2951dbcd8dc33f9dfb842212e788 I am sure it is far from perfect and I would appreciate any feedback (can be given directly for the steps). In my experience people often have problems understanding what exactly the rules mean and experienced TDD programmers tend to fake it – in my understanding of “TDD as if you meant it”. Therefore I tried to show how it could be done, so that everybody can see the single steps: http://www.codersdojo.com/statistics/f80623b0fc6c2951dbcd8dc33f9dfb842212e788

I am sure it is far from perfect and I would appreciate any feedback (can be given directly for the steps).

]]> By: Johan Martinsson http://gojko.net/2009/08/02/tdd-as-if-you-meant-it-revisited/comment-page-1/#comment-76920 Johan Martinsson Fri, 12 Mar 2010 08:42:11 +0000 http://gojko.net/?p=1035#comment-76920 We're trying this exercise in our local ( http://groups.google.fr/group/cara-dojo ). And I have some questions, the most important one being : where do encapsulation come from? In my result I have no objects with state, and I expose simple types (List of integers) everywhere. It seems unnatural, however if I strictly follow the 'rules' well I don't see how a object Field or Player would spring up. Sure the resulting code is very simple. And I do see the benefit of the extremely incremental nature of it. But I'm unhappy about the lack of encapsulation in the result. If someone could have a quick look I'd very much appreciate it. http://github.com/martinsson/cara-dojos/blob/master/ticTacToe/src/main/java/ticTacToe/Game.java http://github.com/martinsson/cara-dojos/blob/master/ticTacToe/src/test/java/ticTacToe/TicTacToeTest.java I also found that the coding of implementation IN the test has a backside : I can't code by intent, so I have the impression of tackling all problems at once : what to test and how to write the code. This is to me one of the important benefits of TDD. Anyone felt the same? Will that pass with experience? And yet another question while I'm at it : Once I've moved a function to the implementation class I can still modify it? We’re trying this exercise in our local ( http://groups.google.fr/group/cara-dojo ). And I have some questions, the most important one being : where do encapsulation come from?

In my result I have no objects with state, and I expose simple types (List of integers) everywhere. It seems unnatural, however if I strictly follow the ‘rules’ well I don’t see how a object Field or Player would spring up.

Sure the resulting code is very simple. And I do see the benefit of the extremely incremental nature of it. But I’m unhappy about the lack of encapsulation in the result. If someone could have a quick look I’d very much appreciate it.

http://github.com/martinsson/cara-dojos/blob/master/ticTacToe/src/main/java/ticTacToe/Game.java
http://github.com/martinsson/cara-dojos/blob/master/ticTacToe/src/test/java/ticTacToe/TicTacToeTest.java

I also found that the coding of implementation IN the test has a backside : I can’t code by intent, so I have the impression of tackling all problems at once : what to test and how to write the code. This is to me one of the important benefits of TDD. Anyone felt the same? Will that pass with experience?

And yet another question while I’m at it : Once I’ve moved a function to the implementation class I can still modify it?

]]> By: Practice, Code Exercises, and Code Katas : Steve Smith's Blog http://gojko.net/2009/08/02/tdd-as-if-you-meant-it-revisited/comment-page-1/#comment-60214 Practice, Code Exercises, and Code Katas : Steve Smith's Blog Tue, 15 Sep 2009 19:45:31 +0000 http://gojko.net/?p=1035#comment-60214 [...] TDD As If You Meant It: Tic-Tac-Toe: A similar writeup, this time using Tic-Tac-Toe. [...] [...] TDD As If You Meant It: Tic-Tac-Toe: A similar writeup, this time using Tic-Tac-Toe. [...]

]]>