> If it's a trivial line of code like a getter or setter that cannot possibly be wrong, then it should be fairly trivial to generate automatically a test case f

> If it's a trivial line of code like a getter or setter that cannot possibly be wrong, then it should be fairly trivial to generate automatically a test case for it. More importantly, if it's a getter or setter, the actual behaviour to be tested is probably broader than "should set/get x." Test scenarios, not methods.