> write tests for methods like getValue() { return value; } Well, if you're just measuring code coverage (which is what clueless management obsesses about), as

> write tests for methods like getValue() { return value; } Well, if you're just measuring code coverage (which is what clueless management obsesses about), as long as something that uses that getter is tested, it will be covered and won't need its own separate unit test. And if it isn't covered, that means you're not using it in which case you can probably get rid of it...