Do we need and ? 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 bring to the table that doesn't?

  • 1
    \$\begingroup\$ I don't think we do, but I can't put my finger on why. \$\endgroup\$
    – Nic
    Jun 21, 2015 at 20:53
  • \$\begingroup\$ @QPaysTaxes I'm feeling the same way. I was having a hard time articulating myself, so I put it out here for discussion. \$\endgroup\$
    – RubberDuck
    Jun 21, 2015 at 21:10

1 Answer 1


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.

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...

  • a post tagged with without unit tests has an irrelevant tag
  • a post tagged with unit tests without a tag is missing a relevant tag
  • a post tagged contains reviewable unit tests
  • a post tagged is a tautology

Therefore, should be made a synonym of , so as to avoid questions with both tags.


You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .