Support for non-percentage coverage threshold

[ariya]

It could be "minimum uncovered unit". For example, in the case of statement coverage, enforcing 4 out 5 statements can be in the form of:

istanbul check-coverage --statement -1

because only 1 statement should be left uncovered. If someone adds a new line which won't be covered, this triggers the warning.

For some projects, including Esprima itself, this is much more convenient than a percentage-based threshold.

[gotwarlost]

Interesting idea, I agree that there are some use cases for which percents do not make sense

[gotwarlost]

Added in v0.1.26

$ istanbul help check-coverage

Usage: istanbul check-coverage <options> [<include-pattern>]

Options are:

      --statements <threshold>
              statement coverage threshold

      --functions <threshold>
              function coverage threshold

      --branches <threshold>
              branch coverage threshold

      --lines <threshold>
              line coverage threshold

Thresholds, when specified as a positive number are taken to be the minimum percentage required.
When a threshold is specified as a negative number it represents the maximum number of uncovered entities allowed.

For example, --statements 90 implies minimum statement coverage is 90%.
             --statements -10 implies that no more than 10 uncovered statements are allowed

<include-pattern> is a fileset pattern that can be used to select one or more coverage files for merge. This defaults to "**/coverage*.json"

[ariya]

+1 Thank you!