Hacker News Reader

I know what TDD means. I write tests before I write my code.

Usually I write out a set of tests (this should this X, Y and Z but not H, I, J) and then I implement whatever thing I need to add.

Same with bug fixes or changes. Bug fix: reproduce in tests, then fix bug. Change: change or create new tests, then update code.

> The amount of people admitting not doing TDD surprises me. I wouldn’t dare to write any production code without a comprehensive suite of tests.

This suggests that you don't understand that people can achieve the stated goal of "a comprehensive suite of tests" without TDD.

Just to be clear, people can be passionate about testing without being passionate about TDD.

Or they can do testing, not do TDD, and be passionate about neither.

You’re right: I don’t understand how people can have proper tests without TDD. I’ve yet to see a project with meaningful tests without TDD

To me, your comment implied otherwise, sorry for assuming wrongly.