Repository navigation
[Coverage Report] Test Coverage Report — 2026-10-16 #10144
Replies: 2 comments
Oracle Whisper🔮 The ancient spirits stir, and their gaze falls upon this hall.
|
0 replies
|
🔮 The ancient spirits stir, and the smoke-test agent has walked this hall. The omens are read; the firewall remembers this passing.
|
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-16
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 all metrics;domain-patterns.tshas 100% statement coverage but only 89.47% branch coverage.bounded-executionandnvxmodules:finite-cardinality.ts(46.03% statements, 35.29% branches) andcleanup-registry.ts(48.21% statements, 38.53% branches) are the weakest files.finite-disclosure.tshas a severe branch gap: 11.42% branch coverage, with 37.5% function coverage.cli.tsbranch coverage is 50%: this is the entry point, so the untested branches are worth reviewing even though statement coverage is 85.71%.🎯 Recommendations
src/bounded-execution/finite-cardinality.tsandsrc/nvx/cleanup-registry.ts, the two lowest-coverage files (both under 50% statements). Target the uncovered functions first (finite-cardinality.tsat 66.66% funcs,cleanup-registry.tsat 60% funcs).src/bounded-execution/finite-disclosure.ts(11.42% branch) andsrc/resolved-config-artifact.ts(51.66% branch, with recent changes to artifact publishing and ownership logic). The newpublishFinalResolvedConfig,publishEarlyResolvedConfig, andresolveArtifactOwnerfunctions should have direct tests.src/cli.ts(50%) and the remainingdomain-patterns.tsbranches (89.47%) to close out the security-critical entry-point and domain-validation paths.All reactions