> I'm not sure why you bring that up. Sorry, forgot to give more details: a private method with a single line of code. That is: something which can be simply d

> I'm not sure why you bring that up. Sorry, forgot to give more details: a private method with a single line of code. That is: something which can be simply done in the caller. > Of course this sentence seems to capture your thinking: Yes, unit testing can be excessive too. Of course I'm more against zero unit testing than excessive unit testing, but each test is an investment, and the optimal approach is, as usual, somewhere in the middle.