Developers reach deadlines faster if they skip TDD in the same way that skydivers reach the ground faster if they skip parachutes.
Blogroll
-
RSS Links
Archives
Category Archives: TDD
A Quick Design Session
Tuesday, July 25, 2006
The team has identified the tasks for the first iteration and are about ready to go to work on it. Before we continue, we pause to have a quick design session where the major classes of the application are identified. The design session is done collaboratively with several, if not all, team members present.
For this [...]
The First Iteration Plan
Sunday, July 23, 2006
After some time off I return to our XP simulation where I attempt to implement a little messaging application. For the iteration ahead there is only one story planned: “A user can send a text message to another user – the console version.” The story is estimated at 5 points. We have a good idea [...]
Unit Testing and Threads
Wednesday, July 19, 2006
While working on the IM application, a pattern seems to be emerging for the tests that I write. I have an object that is supposed to wait for something to happen, and when that something occurs that object is expected to notify another object by making a call to it. For instance, I have a [...]
GoFixture – Waiting for FitLibrary for Ruby
Sunday, July 2, 2006
I have not been able to find a port of FitLibrary for RubyFit. I especially miss the functionality of DoFixture where you can, amongst other things, write fixture tables that contain rows like this
user
Alice
logs on to server
AliceServer
which I find really easy to read.
DoFixture interpret the first and every second cell after that as a name [...]
Tag-Team Programming
Thursday, May 18, 2006
A while back I got the opportunity to do some coding together with a colleague of mine that works in North Andover. I am situated in Malmö, Sweden, myself so we had a time difference of six hours to overcome. Using tools like NUnit and FIT/Fitnesse we were able to get quite a good flow [...]
Extract Class and Test-Driven Development
Monday, May 15, 2006
The mantra of TDD goes “Red, Green, Refactor!” That is, you write a test that fails, you make that test pass, and then you refactor to remove duplication and other code smells.
It’s a good idea to keep in mind where in the TDD groove one is at each moment, even if the time spent in [...]