[Coverage Report] Test Coverage Report — 2026-06-09 #4623
Replies: 2 comments
-
|
🔮 The ancient spirits stir, and the smoke-test agent has passed through this discussion. The omens are clear: the validation rites were observed, the build held, and the run left only a quiet echo in its wake. 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 were read, the path was traced, and the visit is now sealed.
|
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
📊 Test Coverage Report — 2026-06-09
Overall Coverage
108 test files covering 155 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.ts🛡️ Security-Critical Path Status
src/host-iptables.tssrc/squid-config.tssrc/docker-manager.tssrc/domain-patterns.tssrc/cli.tsAll primary security modules (
host-iptables,squid-config,docker-manager) have 100% coverage. Thecli.tsentry point has a branch gap (1 of 2 branches covered) but the file is only 13 lines — it's the top-levelmain()export/invocation split.📋 Full Coverage Table
View all 130+ files (click to expand)
src/commands/validators/network-options.tssrc/squid-log-reader.tssrc/services/agent-volumes/etc-mounts.tssrc/logs/audit-enricher.tssrc/artifact-preservation.tssrc/cli.tssrc/logs/log-parser.tssrc/squid/policy-manifest.tssrc/services/agent-volumes/docker-host-staging.tssrc/commands/logs-command-helpers.tssrc/dind-bootstrap.tssrc/services/doh-proxy-service.tssrc/commands/validators/log-and-limits.tssrc/services/host-path-prefix.tssrc/config-writer.tssrc/services/api-proxy-service.tssrc/services/agent-volumes/docker-socket.tssrc/logs/log-streamer.tssrc/services/agent-volumes/system-mounts.tssrc/diagnostic-collector.tssrc/commands/build-config.tssrc/commands/validators/agent-options.tssrc/services/agent-volumes/hosts-file.tssrc/services/agent-environment/environment-builder.tssrc/squid/ssl-bump.tssrc/ssl-bump.tssrc/host-env.tssrc/logs/log-aggregator.tssrc/upstream-proxy.tssrc/services/cli-proxy-service.tssrc/commands/main-action.tssrc/container-startup-diagnostics.tssrc/services/agent-volumes/workspace-mounts.tssrc/container-cleanup.tssrc/container-lifecycle.tssrc/compose-sanitizer.tssrc/commands/validators/config-assembly.tssrc/logs/log-formatter.tssrc/domain-patterns.tssrc/services/agent-service.tssrc/config-file.tssrc/rules.tssrc/compose-generator.tssrc/option-parsers.tssrc/host-iptables.tssrc/squid-config.tssrc/docker-manager.tssrc/host-iptables-cleanup.tssrc/host-iptables-network.tssrc/host-iptables-rules.tssrc/host-iptables-shared.tssrc/api-proxy-config.tssrc/cli-options.tssrc/cli-workflow.tssrc/dlp.tssrc/dns-resolver.tssrc/copilot-api-resolver.tssrc/redact-secrets.tssrc/squid/access-rules.tssrc/squid/acl-generator.tssrc/squid/config-generator.tssrc/squid/domain-acl.tssrc/squid/upstream-proxy.tssrc/squid/validation.tssrc/services/agent-volumes/credential-hiding.tssrc/services/squid-service.ts🔍 Notable Findings
1.
src/commands/validators/network-options.ts— 50% branch coverage (5/10)The uncovered branches are the DinD/ARC-related warning paths inside
validateNetworkOptions: the!dockerHostCheck.validwarning block and thedindHint && !dockerHostPathPrefixmulti-line warning. These branches guard important user-facing warnings for split-filesystem setups. Tests should simulate an external/non-standardDOCKER_HOSTto exercise these paths.2.
src/logs/log-parser.ts— 69% branch coverage (48/70)22 uncovered branches in log parsing logic suggest missing tests for malformed or unusual Squid log entries — truncated lines, missing fields, non-standard status codes, and edge-case timestamp formats. These gaps won't affect security directly but could produce silent parse failures in
awf logscommands.3.
src/dind-bootstrap.ts— 67% branch coverage (22/33)The DinD bootstrap has 11 uncovered branches. Likely untested: failure paths when bootstrap probes time out, when the Docker socket is unreachable, or when pre-checks fail. Given the DinD flow is critical for ARC runners, these should be covered.
4.
src/services/api-proxy-service.ts— 50% branch coverage (1/2)Only 1 of 2 branches covered in this 43-line file. The recent commit (#4592) refactored
collectRequestBody/transformRequestBodyinto separate functions; the extracted helpers appear well-tested in dedicated test files, but the top-levelbuildApiProxyServiceconditional path may have a gap.📈 Recommendations
High: Cover the DinD warning branches in
src/commands/validators/network-options.ts— mockDOCKER_HOSTto a TCP/non-standard socket invalidateNetworkOptionstests to hit the!validanddindHintwarning paths.Medium: Add edge-case tests for
src/logs/log-parser.ts— focus on malformed log lines (missing host header, truncated entries, IPv6 addresses) to close the 22 uncovered branches.Medium: Expand
src/dind-bootstrap.tstests to cover failure/timeout paths — simulate a Docker socket that is unreachable or responds with an error.Low: Add a test for the error branch in
src/services/api-proxy-service.tsto bring it from 50% to full branch coverage.Generated by test-coverage-reporter workflow. Trigger:
push· Run: 27231888984Beta Was this translation helpful? Give feedback.
All reactions