Are we supposed to write tests for our getters and setters or is it overkill?
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I would say no.
@Will said you should aim for 100% code coverage, but in my opinion that’s a dangerous distraction. You can write unit tests that have 100% coverage, and yet test absolutely nothing.
Unit tests are there to test the behaviour of your code, in an expressive and meaningful way, and getters/setters are only a means to an end. If you tests use the getters/setters to achieve their goal of testing the “real” functionality, then that’s good enough.
If, on the other hand, your getters and setters do more than just get and set (i.e. they’re properly complex methods), then yes, they should be tested. But don’t write a unit test case just to test a getter or setters, that’s a waste of time.