[Coverage Report] Test Coverage Report — 2026-05-29 #4016
Replies: 3 comments
-
|
🔮 The ancient spirits stir; the smoke test agent passed through this discussion and left its omen. 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.
-
|
🔮 The ancient spirits stir, and the smoke test agent has passed through this discussion. The omens are logged, the path is verified, and the watch continues. 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.
-
|
This discussion was automatically closed because it expired on 2026-06-05T14:51:25.216Z.
|
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Overall Coverage
Overall coverage is excellent. 92 test files cover 138 source files.
🔴 Critical Gaps (< 50% statement coverage)
None. All files are above 50% statement coverage.
🟡 Low Coverage (50–79% statement coverage)
src/commands/validators/network-options.tsThis is the only file below 80%. It validates network-related CLI options and has uncovered error-handling branches.
🛡️ Security-Critical Path Status
src/host-iptables.tssrc/host-iptables-rules.tssrc/host-iptables-shared.tssrc/host-iptables-cleanup.tssrc/host-iptables-network.tssrc/squid-config.tssrc/squid/config-generator.tssrc/squid/domain-acl.tssrc/squid/acl-generator.tssrc/squid/access-rules.tssrc/docker-manager.tssrc/domain-patterns.tssrc/cli.tsAll security-critical network isolation and domain filtering paths are extremely well tested.
src/cli.tshas a branch coverage gap (50%), but this file is a thin entry point (7 lines total).📋 Full Coverage Table
Click to expand — all 113 files sorted by statement coverage
src/commands/validators/network-options.tssrc/logs/audit-enricher.tssrc/cli.tssrc/logs/log-parser.tssrc/squid/policy-manifest.tssrc/services/agent-volumes/docker-host-staging.tssrc/commands/logs-command-helpers.tssrc/services/doh-proxy-service.tssrc/container-cleanup.tssrc/services/host-path-prefix.tssrc/config-writer.tssrc/services/agent-volumes/docker-socket.tssrc/logs/log-streamer.tssrc/commands/validators/agent-options.tssrc/cli-options.tssrc/services/agent-volumes/hosts-file.tssrc/services/agent-environment/environment-builder.tssrc/squid/ssl-bump.tssrc/ssl-bump.tssrc/host-env.tssrc/container-lifecycle.tssrc/logs/log-aggregator.tssrc/upstream-proxy.tssrc/commands/validators/log-and-limits.tssrc/commands/main-action.tssrc/services/cli-proxy-service.tssrc/parsers/volume-parsers.tssrc/services/agent-volumes/workspace-mounts.tssrc/pid-tracker.tssrc/commands/validators/config-assembly.tssrc/services/agent-environment/env-passthrough.tssrc/services/agent-volumes/home-strategy.tssrc/logs/log-formatter.tssrc/domain-patterns.tssrc/host-iptables-rules.tssrc/services/agent-service.tssrc/config-file.tssrc/rules.tssrc/compose-generator.tssrc/option-parsers.tssrc/services/api-proxy-service.ts🔍 Notable Findings
src/commands/validators/network-options.ts(66.7% stmts, 50% branch) — The only file below 80%. As a validator for network CLI options (e.g.,--allow-domains,--dns-servers), uncovered branches here could silently accept invalid input. Worth prioritizing.src/logs/log-parser.ts(86.9% stmts, 67.1% branch) — Log parsing has several uncovered branches. Malformed log lines could cause silent failures inawf logs stats/summaryoutput.src/cli-options.ts(93%, 60% branch, 25% functions) — Only 1 of 4 functions is covered. This file parses CLI option defaults; uncovered functions likely represent edge-case option combinations that could bypass validation.src/services/agent-environment/environment-builder.ts(93.5% stmts, 66.7% branch) — The environment builder assembles the agent container's env vars. Uncovered branches could result in missing proxy settings or unexpected credential exposure.📈 Recommendations
High —
network-options.tsvalidator branches: Add tests for invalid--allow-domainsinput (empty string, malformed entries, IPv6 addresses) and invalid--dns-serverscombinations. This is a security input-validation path.Medium —
log-parser.tsbranch coverage (67%): Add tests for malformed Squid log lines, truncated entries, and non-standard timestamp formats. Robust parsing matters for audit-trail reliability.Medium —
cli-options.tsuncovered functions: The 3 untested functions likely handle edge cases in option defaulting. Add tests for--enable-api-proxycombined with other flags, and for config-file-vs-flag precedence scenarios.Low —
environment-builder.tsbranch gaps (67%): Add tests for the DinD code path and for cases whereGITHUB_ACTIONSenv is set vs. unset to ensure proxy vars are always correctly propagated.Generated by test-coverage-reporter workflow. Trigger:
pushBeta Was this translation helpful? Give feedback.
All reactions