News for hackers. Stuff that matters.
Re:The tragedy of 100% code coverage (2016) by tracker1 on Tuesday May 09, 2017 @11:46PM (#14305788)
I think that depends on the language/environment... for example, it's usually MUCH easier to get high coverage, and to do just enough mocking testing against Node-style modules in JS than logic in a typical C# or Java project.

Usually because interfaces need to be clearly/well defined and overridden... In JS there are tools (rewire, proxyquire, etc) that can be used with tests in order to easily inject/replace dependencies without having to write code to support DI nearly as much. In fact, I'd say that there's usually no reason not to be very close to 100% coverage in JS projects.

There are no comments on this comment yet.