Repository navigation
[Coverage Report] Test Coverage Report — 2026-10-14 #10000
Closed
Replies: 1 comment
|
This discussion was automatically closed because it expired on 2026-10-21T23:33:12.240Z.
|
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
📊 Test Coverage Report — 2026-10-14
Overall Coverage
🛡️ Security-Critical Path Status
📋 Coverage Table
🔧 Function Audit
📅 Recent Source Changes (last 7 days)
🔎 Notable Findings
host-iptables.ts,squid-config.ts, anddocker-manager.tsare at 100% across statements, branches, and functions.bounded-execution/finite-cardinality.ts(46% statements, 35% branches) andnvx/cleanup-registry.ts(48% statements, 39% branches) are the lowest-covered files.cli.tsbranch coverage is 50%: statements are 85.71%, so the orchestration entry point has many untested conditional paths.domain-patterns.tshas 89.47% branch coverage: the uncovered branches sit in the domain validation logic that feeds Squid ACL generation.bounded-execution/finite-disclosure.tshas 11.42% branch coverage: most of its conditional logic is unexercised.🎯 Recommendations
src/bounded-execution/finite-cardinality.tsandsrc/nvx/cleanup-registry.ts. Both are below 50% statement coverage. Target the uncovered branches first (cardinality limit edges, and cleanup-registry error and empty-state paths).src/cli.ts(50%) andsrc/domain-patterns.ts(89.47%). Add tests for the error and option-combination branches incli.ts, and for the uncovered validation branches indomain-patterns.ts, since these affect the firewall's domain allowlist.src/bounded-execution/finite-disclosure.ts(11.42% branch) andsrc/microvm/network-reservation.ts(54.86% branch). Add table-driven tests for the disclosure branch variants and for reservation conflict paths.Generated by test-coverage-reporter workflow. Trigger:
pushAll reactions