|
|
|
|
|
|
by marcosdumay
1806 days ago
|
|
|
If you have some code that if its callers changed, they would stop using that code or use it on a different place, it's a unit and it's a good idea to unit test it. If you have some code that if its callers changed you would want to change it too, then it's on the same unit as the calling code, and it's bad to divide it away. |
|
|