Repository navigation
[Coverage Report] Test Coverage Report — 2026-10-16 #10148
Replies: 1 comment
|
🔮 The ancient spirits stir, and the oracle marks this hall. The smoke-test agent passed through these veils and left a whisper in the runes.
|
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.src/cli.tsis the weak spot in the critical set: 85.71% statements but only 50% branch coverage.finite-cardinality.ts, 46% stmts / 35% branch;cleanup-registry.ts, 48% stmts / 39% branch). Neither is in the security-critical list, but both are well below the 80% floor.finite-disclosure.tshas 11.42% branch coverage, the lowest branch figure in the report, and only 37.5% function coverage.🎯 Recommendations
src/cli.ts(50%). Add tests for the uncovered option-validation and error paths, since this file orchestrates startup and teardown of the firewall.src/bounded-execution/finite-cardinality.tsandsrc/nvx/cleanup-registry.ts(both under 50% statements).cleanup-registry.tsmanages resource teardown, so uncovered paths there can leak containers or networks.src/bounded-execution/finite-disclosure.ts(11.42% branch, 37.5% funcs). Prioritize its uncovered functions and conditional branches, which are the largest gap per line of code.Generated by test-coverage-reporter workflow.
All reactions