Repository navigation
[Coverage Report] Test Coverage Report — 2026-10-14 #10001
Closed
Replies: 1 comment
|
This discussion was automatically closed because it expired on 2026-10-21T23:48:07.355Z.
|
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.
Overall Coverage
🛡️ Security-Critical Path Status
📋 Coverage Table
🔧 Function Audit
📅 Recent Source Changes (last 7 days)
🔎 Notable Findings
host-iptables.ts,squid-config.ts,docker-manager.ts,domain-patterns.ts,cli.ts) meet the 100% statement/function bar, thoughcli.tsbranch coverage is only 50%.src/bounded-execution/finite-cardinality.ts(46% statements) andsrc/nvx/cleanup-registry.ts(48% statements) are the largest gaps overall.src/bounded-execution/finite-disclosure.tshas only 11.42% branch coverage, the lowest branch figure in the report.domain-patterns.tshas 89.47% branch coverage, with an uncoveredifandswitchbranch, which matters for domain validation.🎯 Recommendations
src/cli.tsbranch coverage (50%). Add tests for uncovered option-validation and orchestration branches, since this is the entry point.src/domain-patterns.tsremaining branches (89.47%). Add tests for the uncoveredifandswitchpaths, focusing on malformed and edge-case domain inputs.src/bounded-execution/finite-cardinality.tsandsrc/nvx/cleanup-registry.ts. Both sit below 50% statement coverage; prioritize the cleanup/teardown paths.Generated by test-coverage-reporter workflow. Trigger:
pushAll reactions