Repository navigation
[Coverage Report] Test Coverage Report — 2026-10-16 #10101
Closed
Replies: 1 comment
|
This discussion was automatically closed because it expired on 2026-10-23T16:27:45.339Z.
|
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
The per-function audit for
host-iptables.tsandsquid-config.tsreturned no output, so function-level coverage for those files is not verified beyond the file-level 100% figures above.📅 Recent Source Changes (last 7 days)
🔎 Notable Findings
host-iptables.ts,squid-config.ts, anddocker-manager.tsare at 100% for statements, branches, and functions.domain-patterns.tsis at 100% statements but 89.47% branches.src/cli.tsbranch coverage is 50% despite its "OK" status, and it is the main entry point.src/bounded-execution/finite-cardinality.ts(46.03% statements, 35.29% branches) andsrc/nvx/cleanup-registry.ts(48.21% statements, 38.53% branches).src/bounded-execution/finite-disclosure.tshas 11.42% branch coverage, the lowest branch figure in the report.src/resolved-config-artifact.ts(55.33% statements) includes the newly added artifact-publishing and file-permission functions.🎯 Recommendations
src/cli.tsbranch coverage above 50%. It is the main entry point and the only security-critical file with a branch figure that low. Add tests for the uncovered error and option-handling branches.src/nvx/cleanup-registry.tsandsrc/bounded-execution/finite-cardinality.ts. Both are below 50% statements. Cover the cleanup and cardinality-limit paths, including failure cases.src/resolved-config-artifact.tscoveringpublishFinalResolvedConfig,publishEarlyResolvedConfig, andassertPersistentDebugArtifactsIsolated, since these are new and touch file permissions and artifact isolation.Generated by the test-coverage-reporter workflow.
All reactions