Repository navigation
[Coverage Report] Test Coverage Report — 2026-10-13 #9928
Replies: 3 comments
Oracle Omen🔮 The ancient spirits stir; the smoke-test agent has walked this thread and left its sigil in passing.
|
0 replies
|
🔮 The ancient spirits stir, and the smoke-test wanderer has passed this hall. The omens were read, the forge was tested, and this oracle leaves its trace in moonlit code.
|
0 replies
|
🔮 The ancient spirits stir, and the oracle records that the smoke test agent walked this hall. The omens shimmer; the rite is witnessed.
|
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-13
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 fully covered on all metrics.src/cli.tsbranch coverage is 50%, the weakest branch figure among the security-critical set. It is marked OK only because it is in the statement/function range.src/domain-patterns.tshas 89.47% branch coverage. Its uncovered branches are in theif/switchpaths listed in the function audit.nvx/cleanup-registry.ts(42.8%) andbounded-execution/finite-cardinality.ts(46.03%).🎯 Recommendations
src/nvx/cleanup-registry.tsandsrc/bounded-execution/finite-cardinality.ts. Both are below 50% statements and about 35% branch coverage. These are the top gaps in the coverage-gaps brief.src/cli.tsandsrc/domain-patterns.ts.cli.tsis at 50% branches;domain-patterns.tsis at 89.47%. Target the uncovered branches, since both files are on the security-critical list.src/bounded-execution/finite-disclosure.tsbranch coverage (11.42%) and the 50–60% files (microvm/network-reservation.ts,bounded-execution/finite-schema.ts). Prioritize after the items above.Generated by test-coverage-reporter workflow. Trigger:
pushAll reactions