This time a posting from Mark Seemann has raised a slew of comments.

One of them is a note from Colin Jack about the annoyance of producing interface/implementation pairs all the time. My first response is that that sounds to me a bit like a problem with style. Maybe it's just wordplay, but usually I don't extract interfaces from classes, I implement interfaces that I've already discovered in some previous test.

I've had an intense week. Wednesday I was a guest lecturer at Oxford University for their Agile Methods course. The primary lecturer for the course was Angela Martin, who had asked me a while back to talk on Test Driven Development.

Then, I was off to Somerset to run a two day Agile Testing course for a client with Rachel Davies as both my training mentor and co-trainer.

When doing Acceptance Test Driven Development, one of the things that people find hard to understand at first is the nature of an acceptance test.

In the process of teaching it over the last few days, combined with my own experience and some of the discussions during the Agile Alliance Test Tools workshop I've found another way of helping people to understand how to write 'good' acceptance tests.