Skip to main content
Tweeted twitter.com/#!/StackCodeReview/status/615366956594659329
deleted 41 characters in body; edited tags; edited title
Source Link
Jamal Mod
  • 35.2k
  • 2
  • 54
  • 106

Do we need TDD[tdd] and UnitTesting[unit-testing]?

It's a pretty straight forward question. 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?

Do we need TDD and UnitTesting?

It's a pretty straight forward question. 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?

Do we need [tdd] and [unit-testing]?

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?

Source Link
RubberDuck
  • 31.2k
  • 1
  • 38
  • 88

Do we need TDD and UnitTesting?

It's a pretty straight forward question. 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?