|
|
|
|
|
|
by rbanffy
3648 days ago
|
|
|
This creates the risk of making what you are doing explicit at the cost of obscuring why you are doing something. I frequently catch tests in code reviews that don't make it clear why something is being tested and what the overall expected result is beyond the effects being tested. |
|
|