[pydry]

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]

Sounds like a “no true Scotsman” fallacy.

[Dylan16807]

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