[Coverage Report] Test Coverage Report — 2026-05-03 #2425
Closed
Replies: 1 comment
-
|
This discussion was automatically closed because it expired on 2026-05-10T12:48:25.990Z.
|
Beta Was this translation helpful? Give feedback.
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
32 source files · 32 test files · suite passes all configured thresholds
🔴 Critical Gaps (< 50% statement coverage)
None. All files are ≥ 59% statement coverage.
🟡 Low Coverage (50–79% statement coverage)
src/cli.tssrc/commands/logs-command-helpers.ts🛡️ Security-Critical Path Status
src/host-iptables.tssrc/squid-config.tssrc/docker-manager.tssrc/domain-patterns.tssrc/cli.ts📋 Full Coverage Table
src/cli.tssrc/commands/logs-command-helpers.tssrc/logs/audit-enricher.tssrc/logs/log-parser.tssrc/logs/log-streamer.tssrc/docker-manager.tssrc/host-iptables.tssrc/cli-workflow.tssrc/ssl-bump.tssrc/logs/log-aggregator.tssrc/upstream-proxy.tssrc/pid-tracker.tssrc/squid-config.tssrc/logs/log-formatter.tssrc/domain-patterns.tssrc/config-file.tssrc/rules.tssrc/dlp.tssrc/dns-resolver.tssrc/image-tag.tssrc/logger.tssrc/redact-secrets.tssrc/schema-validator.tssrc/types.tssrc/commands/logs-audit.tssrc/commands/logs-stats.tssrc/commands/logs-summary.tssrc/commands/logs.tssrc/commands/predownload.tssrc/logs/index.tssrc/logs/log-discovery.tssrc/logs/stats-formatter.ts🔍 Notable Findings
src/cli.ts— low branch coverage (53%): The main entry point has roughly 40% of its branches untested. This includes argument parsing edge cases, signal handling (SIGINT/SIGTERM), and error propagation paths. A single commit was merged in the past 7 days (feat: add 4 agentic code quality workflows) that touchedsrc/cli.ts, potentially adding uncovered branches.src/host-iptables.ts— branch coverage 81%: All 5 exported functions are covered but ~19% of branches are not, likely the IPv6 fallback paths insetupHostIptablesand edge cases incleanupHostIptables/cleanupFirewallNetwork. These are security-critical iptables rules — missed branches could mean untested failure modes.src/logs/log-streamer.ts— function coverage 77.8%: Two or three functions in the log-streamer have zero coverage. Streamer errors (e.g., file-not-found, permission denied) are likely untested.src/commands/logs-stats.ts/logs-summary.ts— branch coverage 50%: Both commands are at 100% statement coverage but only 50% branch coverage, suggesting that only the happy-path format (markdown/pretty) is exercised by tests, whilejsonformat or error cases are not.📈 Recommendations
High —
src/cli.tsbranch coverage: Add tests for the signal-handling paths (SIGINT/SIGTERMin flight),--keep-containerserror cases, and invalid flag combinations. Goal: raise branch coverage from 53% → 75%+.High —
src/host-iptables.tsIPv6 / cleanup branches: Add unit tests that mockgetDockerBridgeGatewayreturningnulland simulatecleanupHostIptableswhen no rules exist (idempotency). Goal: raise branch coverage from 81% → 90%+.Medium —
src/logs/log-streamer.tsmissing functions: Identify the two uncovered functions (likely error/close handlers) and add tests for file-not-found and early-close scenarios.Low —
src/commands/logs-stats.ts/logs-summary.tsJSON format: Add a test that calls each command with--format jsonto cover the remaining 50% of branches.Generated by test-coverage-reporter workflow. Trigger:
scheduleBeta Was this translation helpful? Give feedback.
All reactions