Gojko Adzic

I had a really great time today at Tesco.Com — thanks for inviting me to talk about acceptance testing and thanks again for the champagne. Here are the slides and links from the talk:

• L.G.Shattuck — Communicating Intent and Imparting Presence
• William Crain — The Mission: The Dilemma of Specified Task and Implied Commander’s Intent
• James Shore: How I use Fit
• FitNesse.Org — main FitNesse web site
• Fitnesse.info — Community site with lots of examples
• Fixture gallery — copy-paste examples for all important FIT fixture types

As always, it was a real pleasure to talk at Skills Matter yesterday. Thanks to everyone who attended the talk. There was quite an interest in this talk, and we might do a re-run for the people who could not make it this time. If you’d like to attend a re-run of the talk soon, drop an e-mail to the organisers and I’ll be happy to do it if there is enough interest.

Here are the slides from the talk. The video should be online at skillsmatter.com soon as well (subscribe to the RSS feed to get notified about that).

These are the links that I mentioned in the talk:

• Spring/Hibernate rollback example
• DbFit project pages on FitNesse.info

You might also be interested in checking out Scott Ambler’s agiledata.org site.

One of central agile programming ideas is to deliver frequently and get feedback early. To get the full benefits of this approach, it is not enough just to make sure that we deliver often and seek feedback — it is extremely important to plan our deliveries correctly as well. If the deliverables are not complete in the sense that they can really be used in production, then the feedback is not as relevant as we would like it to be.

Here is a situation I have seen a few times more than I would have wanted: the team and the clients split the whole project into several phases that will be shipped every few weeks; early deliverables mostly provide the plumbing for the later ones, and have only enough user-interfacing functions for the plumbing to be tested functionally. The clients set up and play with each new release. They dutifully give their feedback and participate in testing each time. When the whole thing comes together on the end, it turns out that the system still requires a lot of changes to solve the problem that it was intended for — the iterations and customer feedback failed to provide the directions. Continue Reading »

Here’s the video from last week’s Effective .NET Test Driven Development FitNesse workshop. The workshop focused on introducing agile acceptance testing and working with FitNesse, with best practices and ideas how to use fixtures efficiently. The recording is about two hours long.
See also:

• Key ideas from the workshop
• Source code and the missing example

You can download the complete sourcecode for the examples from the SkillsMatter FitNesse workshop from here. Grab the related fitNesse tests from here. For a list of key ideas to take away from the session, click here.

Unfortunately, we did not have enough time to finish the example of integrating entity classes into FitNesse for .NET during the workshop. So here is the implementation: Continue Reading »