|
|
|
|
|
|
by rochacon
1929 days ago
|
|
|
I share the same opinion. Its been a long time since I read Kent Beck's book on TDD, but I don't recall him saying TDD = unit tests. When I see people using these as synonyms it feels to me they don't quite understood what TDD means and just jumped into this conclusion of "unit tests that check every method/line of code you write". Testing behavior from the user perspective should be the goal, these are the kind of tests that bring most value in the long run. |
|
|
I think a way to smell you're too far gone on this way is when you write tests only to get code coverage.
With behavior tests, code coverage should become a tool to show where your dead code is so you can remove it.