> 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

> 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.