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.
In JUnit FAQ you can read that you shouldn’t test methods that are too simple to break. While all examples seem logical (getters and setters, delegation etc.), I’m not sure I am able to grasp the “can’t break on its own” concept in full. When would you say that the method “can’t break on its own”? Anyone care to elaborate?
I think “can’t break on its own” means that the method only uses elements of its own class, and does not depend upon the behavior of any other objects/classes, or that it delegates all of its functionality to some other method or class (which presumably has its own tests).
The basic idea is that if you can see everything the method does, without needing to refer to other methods or classes, and you are pretty sure it is correct, then a test is probably not necessary.
There is not necessarily a clear line here. “Too simple to break” is in the eye of the beholder.