[Coverage Report] Test Coverage Report — 2026-06-06 #4460
Replies: 4 comments
-
|
🔮 The ancient spirits stir: the smoke test agent was here, and the run remains under watchful stars. 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. May the build winds remain 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.
-
|
🔮 The ancient spirits stir above the archived currents. A smoke test agent passed through this discussion and left a luminous trace upon the winds. 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-13T18:38:59.023Z.
|
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Overall Coverage
105 test files · 153 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.tsAll four primary security-critical modules are at or near 100%. No regressions detected.
📋 Files with Branch Coverage < 70% (non-test-utilities)
src/commands/validators/network-options.tssrc/services/api-proxy-service.ts!networkConfig.proxyIperror throw (L32–33)src/dind-bootstrap.tssrc/logs/log-parser.tsdestentries (L178–202)src/services/agent-environment/environment-builder.tssrc/services/agent-volumes/etc-mounts.ts📋 Full coverage table (files with < 100% or branch gaps)
🔍 Notable Findings
src/commands/validators/network-options.ts— Docker host warning paths untested (50% branch)Lines 47–74 cover three
logger.warn()branches triggered by external Docker hosts and DinD hinting. Since these fire only in ARC/DinD environments, they are hard to exercise in unit tests. Adding a test that mockscheckDockerHost()to return{ valid: false }andresolveDockerHostPathPrefix()to return adindHint: trueresult would bring this module to near 100%.src/services/api-proxy-service.ts— Missing guard test (50% branch)The defensive
if (!networkConfig.proxyIp) throwat line 32 is the only uncovered path. A single unit test passingnetworkConfigwithoutproxyIpwould cover it and guard this error path going forward.src/logs/log-parser.ts— IPv6 dest parsing uncovered (67% branch)The bracketed IPv6 address parser (
[2001:db8::1]:443format) at lines 178–195 has no test coverage. This path is exercised only when Squid logs IPv6 upstream destinations. Adding fixture log entries with IPv6 addresses would cover these branches.src/services/agent-volumes/etc-mounts.ts— Error-path catch blocks uncovered (68% branch)readFileContent()andwriteTempFile()both havecatch { return undefined }branches at lines 20, 28, 53–57 that are never exercised. Mockingfs.readFileSync/fs.writeFileSyncto throw would cover these defensive paths and harden the/etcmount logic.📈 Recommendations
High — Add Docker host warning tests to
network-options.ts: Lift statement coverage from 66% to ~95% and branch coverage from 50% to ~90% with 2–3 unit tests mockingcheckDockerHost()andresolveDockerHostPathPrefix().Medium — Cover error paths in
etc-mounts.ts: Mockfsfailures forreadFileContent/writeTempFile; improves resilience testing for the/etcbind mount construction path.Medium — Add IPv6 log fixtures to
log-parser.ts: Extend existing Squid log fixture data with bracketed IPv6 entries ([::1]:443); covers the only missing parser branches.Low — Add guard test for
api-proxy-service.ts: Single test case withproxyIp: undefinedcovers the last uncovered branch in a security-relevant module.Generated by test-coverage-reporter workflow. Trigger:
push· Run: 27070476108Beta Was this translation helpful? Give feedback.
All reactions