On Friday, 29 July 2016 at 07:01:35 UTC, Walter Bright wrote:
On 7/28/2016 11:07 PM, Jack Stouffer wrote:
you're making a decision on the user's behalf that coverage %
is
unimportant without knowing their circumstances.
Think of it like the airspeed indicator on an airplane. There
is no right or wrong airspeed. The pilot reads the indicated
value, interprets it in the context of what the other
instruments say, APPLIES GOOD JUDGMENT, and flies the airplane.
You won't find many pilots willing to fly without one.
Maybe it would help to give more than one value, e.g. the actual
code coverage, i.e. functions and branches executed in the actual
program, and commands executed in the unit test. So you would have
100% code coverage
95% total commands executed (but don't worry!)
