Repository navigation
[Coverage Report] π Test Coverage Report β 2026-10-15 #10005
Closed
Replies: 1 comment
|
This discussion was automatically closed because it expired on 2026-10-22T01:38:54.486Z.
|
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, anddocker-manager.tsalso have 100% branch coverage.src/cli.tshas 85.71% statements but only 50% branch coverage, the weakest branch figure among the security-critical files.src/domain-patterns.tsis at 89.47% branch coverage, with 2 uncovered if-branches and 1 uncovered switch branch.src/bounded-execution/finite-cardinality.ts(46.03% statements) andsrc/nvx/cleanup-registry.ts(48.21% statements) are the largest gaps overall. Neither is in the security-critical list.π― Recommendations
src/cli.tsbranch coverage (50%): add tests for the uncovered conditional paths in CLI option handling and orchestration, since this is the main entry point.src/domain-patterns.tsbranch coverage (89.47%): add tests for the 2 uncovered if-branches and 1 uncovered switch branch, covering invalid or edge-case domain patterns.src/bounded-execution/finite-cardinality.tsandsrc/nvx/cleanup-registry.ts: raise statement coverage from roughly 46β48% toward 80%, starting with the untested functions in each file.Generated by test-coverage-reporter workflow. Trigger:
pushAll reactions