Executable ranges
Measured67 of 67 known ranges covered · Total gate disabled
Node.js 24.19.0 · native V8 coverage
vanilla-test Node native V8 coverage
Coverage calculated directly from the executable ranges reported by V8.
The source ran as written—without source instrumentation, transpilation, or runtime rewriting.
Coverage gates passedEvery enabled total and per-file gate is satisfied.
100%
Block ranges
Measured52 of 52 known ranges covered · Total gate disabled
Function ranges
Measured15 of 15 known ranges covered · Total gate disabled
Executable lines
Measured231 of 231 known ranges covered · Total gate disabled
Thresholds
Total: not enforced · Per file: enforced
| Metric | Minimum | Total | Per file |
|---|---|---|---|
| Executable ranges | 100% | Not enforced | Pass |
| Block ranges | 100% | Not enforced | Pass |
| Function ranges | 100% | Not enforced | Pass |
| Executable lines | 100% | Not enforced | Pass |
Files
2 sources measured
| Source | V8 state | Executable ranges | Block ranges | Function ranges | Executable lines |
|---|---|---|---|---|---|
cmd.js | Loaded | 100%66 / 66 | 100%52 / 52 | 100%14 / 14 | 100%207 / 207 |
cmd.mjs | Loaded | 100%1 / 1 | 100%0 / 0 | 100%1 / 1 | 100%24 / 24 |
How these metrics work
Transparent range semantics
| Executable ranges | One item for every executable range record emitted by V8, including function roots and nested block ranges; a positive execution count is covered. V8 may collapse equal-count ranges, so totals can vary with the execution path. |
|---|---|
| Block ranges | One item for every nested block range after a function root range; a positive execution count is covered. These are count-change regions, not parser-enumerated branch alternatives. |
| Function ranges | One item for the first (root) range of every V8 function record; a positive execution count is covered. |
| Executable lines | One item for every source line whose content intersects an effective executable range; a line is covered only when every intersecting effective range has a positive count. |
| Effective ranges | Source is partitioned at every V8 range boundary. Each segment uses the count from its smallest enclosing range, with the lowest count winning an equal-size tie. |
| Output interoperability | The JSON and LCOV files use conventional field names and records for tool transport, but executable-range and block-range totals are native V8 measurements and are not interchangeable with parser-derived statement or branch totals. Summary pct values are truncated to two decimals; threshold gates compare the exact covered/total ratio. |
| Included, not loaded | An included file not emitted by V8 is represented by one zero-count whole-file range. Its internal function and block structure is unknown and cannot satisfy a positive function or block threshold. |
These measurements deliberately describe V8 ranges. They do not claim parser-derived statement or branch semantics.