Hello world: reading JavaScript coverage
Read the missed outcomes before deciding what a coverage percentage means.
The September 2019 archive inventory records this blog URL on istanbul.js.org. It supplies capture dates rather than the article body. This is a new independent introduction to the coverage topics documented by the project.
Separate execution from correctness
Coverage records execution of instrumented code. Assertions check the behavior you expect. A line can run without an assertion checking its result, and one line can contain more than one branch outcome.
Inspect the per-file report and compare it with the test inputs. Then check the included source files and the process that collected the counters. Different source scopes can produce percentages that are unsuitable for comparison.
Continue with report formats, the Mocha example or threshold policy. The first-report note provides a starting sequence.