3 ms·
Unit tests tie you down to the specific implementation, which means changing the implementation becomes much more onerous. If you test unit interfaces and not
by Silhouette 3y ago
Unit tests tie you down to the specific implementation, which means changing the implementation becomes much more onerous.
If you test unit interfaces and not implementation details then that problem goes away.
- recursive 3y agoUnit tests tie you down to a specific problem decomposition.
- Silhouette 3y agoUnits give you a specific problem decomposition. Unit tests just help to make sure that the units you have right now are doing their jobs. Obviously if you change what units you have or how responsibilities are allocated among them then you will need corresponding changes in the unit tests.
- bluGill 3y agoWhich is good only if you have the comprehensive integration tests as well.
- Silhouette 3y agoI don't see why. There are some type of code where I think unit testing is very beneficial and other types of code where I'd probably prefer a different style of testing. But for code where unit testing helps I find it useful independent of any of other types of testing that may or may not be happening as well.