Repository navigation
[Coverage Report] Test Coverage Report — 2026-10-11 #9808
Closed
Replies: 1 comment
|
This discussion was automatically closed because it expired on 2026-10-18T04:52:01.763Z.
|
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-11
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.tsalso have 100% branch coverage.src/cli.tshas the weakest security-critical branch coverage at 50% (statements 85.71%).src/domain-patterns.tsis at 89.47% branch coverage, the only security-critical file below 100% branch coverage.src/nvx/cleanup-registry.ts(42.8% statements) andsrc/bounded-execution/finite-cardinality.ts(46.03% statements). Both are flagged CRITICAL in the gaps brief.🎯 Recommendations
src/cli.ts(50% branch coverage), focusing on error and signal-handling paths in the orchestration flow.src/nvx/cleanup-registry.ts(42.8% statements, 32.11% branches) to cover its cleanup paths.src/domain-patterns.tsbranch coverage from 89.47% to 100%, and add tests forsrc/bounded-execution/finite-cardinality.ts(46.03% statements, 35.29% branches).Generated by test-coverage-reporter workflow. Trigger:
scheduleAll reactions