Controversial opinion: for new projects I mandate 100% coverage from unit tests and Mutation tests. In my book, if something is testable there's no reason not to test it. If its too difficult to test then that's a code smell. The big benefit my team gets from having complete high quality coverage is the ability to permit automated dependency updates and deployments so out projects are always up to date with security patches. Granted, this could lead to problems with malicious actors publishing a nefarious package, but we're already trusting vendors not to do that and nobody is reviewing every LOC they pull in from dependencies. So far, this mechanism seems to be working well.
![php[architect]](http://yt3.ggpht.com/17sMZ4iyRjqC_0z8qO5w-9AhAM1r_O9v_aGLvBcK5kykGsbV54jIrhXhjDf3EIbiMWp-ZkwckA=s48-c-k-c0x00ffffff-no-rj)
Controversial opinion: for new projects I mandate 100% coverage from unit tests and Mutation tests.
In my book, if something is testable there's no reason not to test it. If its too difficult to test then that's a code smell.
The big benefit my team gets from having complete high quality coverage is the ability to permit automated dependency updates and deployments so out projects are always up to date with security patches.
Granted, this could lead to problems with malicious actors publishing a nefarious package, but we're already trusting vendors not to do that and nobody is reviewing every LOC they pull in from dependencies. So far, this mechanism seems to be working well.