Repository navigation
[Coverage Report] Test Coverage Report — 2026-10-14 #9986
Closed
Replies: 1 comment
|
This discussion was automatically closed because it expired on 2026-10-21T17:08:35.734Z.
|
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-14
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 statements, branches, and functions.cli.tshas 50% branch coverage anddomain-patterns.tshas 89.47%. Thedomain-patterns.tsreport shows 2 uncoveredifbranches and 1 uncoveredswitchbranch.bounded-execution/finite-cardinality.ts(46% statements, 35% branches) andnvx/cleanup-registry.ts(48% statements, 39% branches) are the lowest-covered files. Both are below 50% statement coverage.bounded-execution/finite-disclosure.tshas an extreme branch gap. It shows 11.42% branch coverage with 37.5% function coverage.🎯 Recommendations
src/cli.tsandsrc/domain-patterns.ts. Cover the uncoveredifandswitchbranches indomain-patterns.ts(for example, invalid or edge-case domain inputs) and the untested branches incli.ts. These sit on the domain-allowlist path, so they are the most security-relevant gaps.src/bounded-execution/finite-cardinality.tsandsrc/nvx/cleanup-registry.tsabove 80%. Both are under 50% statement coverage. Add tests for their uncovered functions and error paths, starting withcleanup-registry.ts, where cleanup failures could leave resources behind.src/bounded-execution/finite-disclosure.ts. Its 11% branch coverage and 37.5% function coverage suggest most decision logic is untested. Prioritize the branch paths that decide what gets disclosed.Generated by test-coverage-reporter workflow. Trigger:
pushAll reactions