undefined | Better HN

0 pointspydry10mo ago0 comments

The definition is you write or amend a test before making the code change that makes it pass.

That's it. It says nothing about the type of test you write. Personally i do it with literally every type of test that i write - acceptance, integration, unit.

If you write a decent test, yes, TDD is always valuable. If you TDD with shitty tests, not so much, but that isnt really an issue with TDD.

0 comments

cjbgkagh10mo ago

Sounds like a “no true Scotsman” fallacy.

Dylan1680710mo ago

It's not. "Doing C before doing Y is beneficial but requires you to be competent at C." is not a no true Scotsman.

j / k navigate · click thread line to collapse

0 comments

cjbgkagh10mo ago

Sounds like a “no true Scotsman” fallacy.

Dylan1680710mo ago

It's not. "Doing C before doing Y is beneficial but requires you to be competent at C." is not a no true Scotsman.

j / k navigate · click thread line to collapse