|
|
|
|
|
|
by suction
1386 days ago
|
|
|
A very good explanation. Yet what I think is confusing a lot of (very?) good programmers (not me) is that they already do that intuitively by not letting methods become longer than 3 or 4 lines, and whenever implementing a new method, by writing the return statement first (i.e. returning a mock object or similar) and working backwards, i.e. only writing enough code to be able to return the desired value. If one then goes and tries to write tests for these kind of methods, it feels like superfluous busywork. |
|
|