Do we need tdd and unit-testing? I understand that they're not synonymous in the real world. One can unit test without testing first, but do we require this fine grain distinction between the two?
In the context of a code review, what does tdd bring to the table that unit-testing doesn't?
tdd is an indication of how OP's code was written - unit tests first. By itself alongside a language tag, it doesn't bring anything to the table IMO.
unit-testing on the other hand, tells us that OP has unit tests, at least as part of the reviewable code - regardless of whether the code was written with TDD or not.
Since the code is already written, working and tested, whether it was done TDD, OOP and DRY is irrelevant, especially if the unit tests aren't included in the OP.
Bottom line...
Therefore, tdd should be made a synonym of unit-testing, so as to avoid questions with both tags.
