Skip to content

Comment on TDD is Behavior Specificationparent

Comments

I was around when the term TDD first appeared. And I don't think that originally it meant anything more than what you are proposing.

But then some dudes came along and said: "This is awesome, lets make it better!"

And before one could blink, a concept of 100% coverage was born. From there on everything went full retard.

I completely agree that TDD originally meant that, and still does. The problem is too many developers don't bother to learn what TDD really means and immediately think of it as a testing methodology because the first word is "test". Maybe changing the language can change the focus to where it was supposed to be from the beginning.

AboutSource Built by g1lg1l

Hackerly is an independent reader for Hacker News, built on the public HN API. Not affiliated with Y Combinator.