The definition is you write or amend a test before making the code change that m... | Hacker News

Hacker Newsnew | past | comments | ask | show | jobs | submit

		pydry 5 months ago \| parent \| context \| favorite \| on: Math.Pow(-1, 2) == -1 in Windows 11 Insider build 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.

cjbgkagh 5 months ago [–]

Sounds like a “no true Scotsman” fallacy.

Dylan16807 5 months 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.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact