|
|
|
|
|
|
by gravypod
1725 days ago
|
|
|
> 100% code coverage is still not a good use of everyone's time in most projects and languages The key here is most. Think about your use case before applying anything you read online. > It's fine that _some_ code has no color at all, while you some other paths to be bright red in the end, instead of always just going for a uniform orange for everything. This was the logic tree of a device used for health care work. Cost of failure was high. I had very good coverage of all edge cases that other systems could produce and tested a lot of extremes + a DSL for describing the input state. The important thing here: an expert system is not most programs and the cost of a failure should really drive what your testing methodology is. |
|
|
Looks like your case is one where 100% coverage is a good thing and the cost paid for it is absolutely acceptable - nay needed to be paid. And you didn't just go for 100% and stop there because you hit some metric but you actually did the thing that's more important too ("data coverage"). Kudos!