I once worked at a place that demanded we write unit tests for every new method. Something that was simply a getter or setter? New unit test. I'd argue that the code was covered by tests on other code, where it was actually used. This would result in more and more useless arguments. Eventually, I just moved on. The company is no longer in business anyway.
I'd argue if you have "getters and setters" you're already doing it wrong, because you're employing OOP. Just use a raw data structure and write functions that accept it as a parameter. Other things being equal, the code will be less complex, cleaner, and easier to test.
I follow the rule that if you have code that was written, it should be tested.
> Something that was simply a getter or setter? New unit test.
Bring in a framework to generate those. You shouldn't be writing them, and if you are it's because they're sepecial.