> So people started writing stupid unit tests for getters and setters in Java DTOs to reach the goal. To me that reads like your team fucked up at a very funda

> So people started writing stupid unit tests for getters and setters in Java DTOs to reach the goal. To me that reads like your team fucked up at a very fundamental level, as they both failed to take into account the whole point of automated tests and also everyone failed to flag those nonsense tests as a critical blocker for the PR. Unless your getters aand setters are dead code, they are already exercised by any test covering the happy path. Also, a 80% coverage target leaves out plenty of headroom to leave out stupid getter/setter tests. A team that pulls this sort of stunt is a team that has opted to develop defensive tricks to preserve their incompetence instead of working on having in place something that actually benefits them.