Statements + lines
Reveal code that never executed. They do not prove that executed behavior was asserted correctly.
Generated Node.js evidence
Coverage
Vanilla Test records native V8 coverage for the 14.x Node.js suite on main. Rust correctness is tracked separately; JavaScript V8 coverage is not presented as Rust coverage.
Latest generated summary
Statements, branches, functions, and lines are loaded from data/coverage-summary.json.
Loading generated workflow data…
No generated coverage summary is available.
No percentage is shown because fabricating or preserving a stale number would be misleading. Run the workflow or npm test to create current evidence.
Browse the report
The rendered report maps every source line to its execution evidence and shows uncovered branches and functions.
If the report link is unavailable
The Pages workflow has not staged coverage for this revision. Run npm test locally, then open the generated coverage/node/ report.
Read coverage with tests
Branches
Reveal missed outcomes in conditionals, error paths, optional parameters, and platform decisions.
Functions
Reveal callable surfaces that no test reached. A called function can still need stronger assertions.
Coverage is evidence, not the correctness count.
It does not add cases to the categorized correctness inventory and never replaces unit, functional, integration, or regression intent.
Generate locally
npm test
# reports are written to coverage/node/The project serves local reports with npm run coverage after the test output exists.