|
|
|
|
|
by nrook
2475 days ago
|
|
There's an insight here I haven't seen elsewhere. Everyone but the most blind ideologue knows 100% test coverage isn't a good use of your time. But it's hard to care about increasing coverage from 89% to 90%, or to feel justified in objecting during a code review because the change under review would decrease coverage from 90% to 89%. The solution to this dilemma is to make it easy to mark code as "OK not to be tested". It's annoying to have test annotations in code, but I'd expect mostly entire modules will be exempted, so it's not that big a deal. And this way, the coder has to either write tests or make a specific decision not to. |
|