istanbul-js
Menu
Advanced reference

Advanced Istanbul coverage: follow the data through each stage

Trace a coverage problem from instrumentation through collection and reporting.

Tests flow through instrumentation and collection before a report is rendered.
Follow the data in order: inserted counters, collected results, then a rendered report.

Did the source receive counters? Did the environment save them? Is the reporter reading the same source revision? These guides follow instrumentation, file selection, collection, output and enforcement.

Choose a stage to inspect

Use a short diagnostic sequence

Identify the instrumenter or runtime provider. Inspect one raw file and its source path. Render it against the matching checkout. Then check whether policy failure comes from aggregate limits, per-file checks or a changed source set.

Keep raw counters separate from summaries. An aggregate number can describe different file sets, and a summary cannot recover the source locations needed to investigate a branch.

Return to runner configuration when needed

If no usable data exists, start with the tutorials. Jest and tap own their coverage controls. Browsers and devices need a transfer step. The integration guide compares those boundaries before you add another wrapper.

Primary sources

Check official documentation against the tools installed in your project. These explanations and examples are independent.