3 ms·
This is TDD? Tests first, then code? I do first the docs, then the tests, then the code. For years. What he describes is like that. Just that the plan step is
by rurban 8mo ago
This is TDD? Tests first, then code?
I do first the docs, then the tests, then the code. For years.
What he describes is like that. Just that the plan step is suggesting docs, not writing actual docs.
- godelski 8mo agoTDD 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.html https://www.cs.utexas.edu/~EWD/transcriptions/EWD02xx/EWD288...
- rurban 8mo agoOf course tests are not proofs. For proofs I do 'make verify' :) Tests just catch the most simple mistakes, edge cases and some regressions.
- godelski 8mo agoSo you're agreeing? The problem with TDD isn't the T it's the (first) D
- UK-Al05 8mo agoIt's not meant to give you complete coverage. It's meant to guide to meeting the acceptance criteria.
- godelski 8mo agoThen you agree. But the existence of unit tests does not mean you're doing TDD.