Either you should have your ide generate your pojo methods, or use lombok. Or use kotlin.
In all cases testing pojos is stupid. Unless you want to test serialization or deserialization but then you are not just testing pojos.
The blind religion of "everything must be tested" is irrelevant in the professional world where developer time is money, and test code must produce sufficient value: if it doesn't, then you are wasting your time. And I also mean to imply that not all tests are created equal not all are equally valuable.
Nope.
Either you should have your ide generate your pojo methods, or use lombok. Or use kotlin.
In all cases testing pojos is stupid. Unless you want to test serialization or deserialization but then you are not just testing pojos.
The blind religion of "everything must be tested" is irrelevant in the professional world where developer time is money, and test code must produce sufficient value: if it doesn't, then you are wasting your time. And I also mean to imply that not all tests are created equal not all are equally valuable.
Why? What's the argument? Let's hear it.