[Coverage Report] Test Coverage Report — 2026-06-09 #4649
Replies: 1 comment
-
|
🔮 The ancient spirits stir: the smoke test agent was here, and the omens are favorable. Warning Firewall blocked 1 domainThe following domain was blocked by the firewall during workflow execution:
network:
allowed:
- defaults
- "registry.npmjs.org"See Network Configuration for more information.
|
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.
-
📊 Test Coverage Report — 2026-06-09
Overall Coverage
135 of 136 measured files are at ≥80% statement coverage.
🔴 Critical Gaps (< 50% statement coverage)
None.
🟡 Low Coverage (50–79% statement coverage)
src/commands/validators/network-options.ts🛡️ Security-Critical Path Status
src/host-iptables.tssrc/squid-config.tssrc/docker-manager.tssrc/domain-patterns.tssrc/cli.tsThe four highest-risk security modules (
host-iptables,squid-config,docker-manager,domain-patterns) are all at ≥95%.src/cli.tsis the only security-adjacent file with a notable gap — 50% branch coverage leaves several orchestration paths (signal handling, flag combinations, cleanup failures) untested.📋 Files With Branch Coverage < 80%
src/cli.tssrc/commands/validators/network-options.tssrc/services/api-proxy-service.tssrc/services/service-test-setup.test-utils.tssrc/services/agent-environment/environment-builder.tssrc/dind-bootstrap.tssrc/services/agent-volumes/etc-mounts.tssrc/logs/log-parser.tssrc/services/agent-volumes/docker-host-staging.tssrc/logs/audit-enricher.tssrc/services/agent-volumes/workspace-mounts.tssrc/services/doh-proxy-service.ts🔍 Notable Findings
src/cli.ts— 50% branch coverage (main orchestrator). Likely uncovered:--enable-api-proxy+--enable-dindinteraction paths, SIGTERM mid-startup handling, and--keep-containerscleanup fallback.src/commands/validators/network-options.ts— 66.66% stmt / 50% branch. This validator guards security-critical CLI options (DNS servers, allowed-domain lists). The uncovered branches are likely invalid-input rejection paths that should be tested to confirm the firewall refuses malformed configurations.src/services/api-proxy-service.ts— 50% branch coverage. The API proxy sidecar injects credentials; half its branches are untested. Likely missing: startup-failure and unhealthy-sidecar paths that are critical to credential-isolation guarantees.149 source files changed in the past 7 days — including a full
logscommand suite and new exports (runMainWorkflow,buildConfig,auditCommand,createMainAction). Overall coverage held steady, suggesting tests were added alongside new code.📈 Recommendations
High — Branch-cover
src/cli.tserror and flag-interaction paths (--enable-api-proxy+--enable-dind, SIGTERM mid-startup, cleanup-failure with--keep-containers).High — Complete
src/commands/validators/network-options.ts— add tests for malformed DNS IPs, invalid upstream proxy URLs, and domain list edge cases. Pure-function unit tests, trivial to add.Medium — Cover
src/services/api-proxy-service.tsfailure paths (sidecar start failure, mid-run unhealthy) to validate credential isolation.Low — Raise branch coverage in
src/logs/log-parser.ts(68.57%) andsrc/logs/audit-enricher.ts(74.13%) with malformed-log-line fixture tests.Generated by test-coverage-reporter · Trigger:
push· 108 test files / 155 source files · Run: 27240750261Beta Was this translation helpful? Give feedback.
All reactions