The problem with Test-driven Development is that it's got the word "test" in the title. It's actually not as much about tetsing your code as it is about using tests to specify what code you should write in the first place. But the presence of the dreaded "T" word confuses the issue, and hampers meaningful discussions or attempts to adopt TDD practices.

So, quite understandably, TDD advocates have been keen to ditch the "T" word to make the practices easier to promote. We now have Behaviour-driven Development, for example. And talking of examples, we also have Example-driven Development.

I have, on occasion, need to rent a holiday home.

Sometimes for a week. Sometimes for a weekend. Sometimes for two weeks - though nowhere near as often as I'd like.

I'm the same with hotel rooms. Sometimes I'm there for a night. Sometimes I'm staying for a week or more when I'm on extended business.

And I don't know about you, but I tend to find that the longer I know I'm going to be there, the more care I tend to take to keep the place tidy, because I know I'll have to live in my mess if I don't.

SQE’s Joey McAllister interviewed me for the March 2008 Gray Matters podcast (click the link for the mp3 file), where we talked about the testingfaqs.org Boneyard and the strength of the worldwide test tools market.

"Microsoft must stop polluting the downstream with patent encumbrances.  Period.  Full stop."

- Matt Assay (Microsoft's dilemma: The importance of the downstream)

STDL (Structured test description language) is a domain-specific testing language that is used to auto-generate unit test code. It supports a myriad of output languages (incl. C#). The project's aim is that of reducing the resources required for testing