3 ms·
This is the correct way, but in my experience less-traveled programmers start striving for that elusive 100% coverage and end up writing unit tests for complete
by theshrike79 6y ago
This is the correct way, but in my experience less-traveled programmers start striving for that elusive 100% coverage and end up writing unit tests for completely obvious stuff like constructors (which do nothing else than setting values) or setters/getters.
- spacekitcat 6y agoDevelopers always have to estimate the cost/benefit of how they're spending their time and overly strict coverage targets get in the way of that. Test coverage targets make very little sense for a statically typed language like C#, a fools errand almost. In dynamically typed languages, it's hard not to almost hit 100% if you're doing some honest TDD. Just for example.