Hey everyone, I am David Heinemarhansen.

I am here with Martin Fowler and Kent Beck to talk about is TDD debt as a topic.

Coming off, keynote I did a RailsConf and some subsequent articles.

I posted on the blog.

I had a chance to talk with both Kent and Martin,

sort of one-on-one in the days the follow,

and we got to discuss a bunch of these issues.

And I got to clarify some thoughts and definitions that I had in my head

and got a lot wiser about where both Martin and Kent are on the issue and

Kent suggested that hey maybe we should share that with the world so that's what we're doing now

I know a bunch of people have been expecting that this was going to be a big Duke out there will be no boxing

we'll explore a bunch of definitions and problems and patterns we've seen

and what's worked for us individually and go from there.

But to get started, I thought I just run over a brief recap of the problems that I've seen with TDD and use that to kick

off the discussion.

And really three major points that I'll focus on for this discussion.

The first is the definition of TDD and its components, specifically unit testing.

I know the TDD and in unit testing is certainly not

the same thing but TDD is often used to to drive your tests and as I was looking

through sort of issues I've been seeing in the rails world around TDD a lot of

that came down to the definition of unit testing.

That people were defining unit testing as, it can't have collaborators, you can't touch the database,

...