Unit Testing Getters and Setters

Interesting one this. I'm sitting here wondering whether to test all my getter and setter methods. Since I let Eclipse do all the work should I test them all? Two theories here. One, Test everything that can go wrong. Two, don't explicitly test them because you'll test them implicitly in the tests for more complex application testing. Further more if I don't use the get/setter in my test code do I need the get/setter in the first place? That's just a bonus.

It seems to me that Scott Leberknight has the right idea. I'd like to see his solution incorporated in JUnit. Then I surfed around and saw that there was some question as to whether get/setters were in fact OO or not. Interesting comments, brighter people than me are suggesting not always. I can see the point. Read the "Why Getter and Setter Methods are Evil" on JavaWorld by Allen Holub and have a think about it.

Now I'm thinking I should revisit the whole thing.