TDD has always been flawed. Tests can't give you complete coverage, they are always incomplete. Though every time I say this people think I'm against tests. I'm just saying tests can't prove correctness. You'd have to be a lunatic to think they are proofs. Even crazier is having the LLMs write their own tests and think that that's proof. I'm sure it improves things, but proofs are a different beast all together.

Seems things still haven't changed in half a century

https://www.cs.utexas.edu/~EWD/transcriptions/EWD02xx/EWD288...

Of course tests are not proofs. For proofs I do 'make verify' :)

Tests just catch the most simple mistakes, edge cases and some regressions.

So you're agreeing? The problem with TDD isn't the T it's the (first) D

It's not meant to give you complete coverage. It's meant to guide to meeting the acceptance criteria.

Then you agree. But the existence of unit tests does not mean you're doing TDD.