[Coverage Report] Test Coverage Report — 2026-06-01 #4136
Replies: 2 comments
-
|
🔮 The ancient spirits stir; the smoke test agent was here. 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 was here. 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.
Uh oh!
There was an error while loading. Please reload this page.
-
📊 Overall Coverage
95 test files covering 142 source files.
🔴 Critical Gaps (< 50% statement coverage)
None. All source 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-critical files (iptables rules, Squid config, domain matching) have 100% coverage.
src/cli.tshas low branch coverage (50%) — the uncovered branches are likely error-handling and signal paths.📋 Full Coverage Table
All files (sorted by statement coverage ascending)
src/commands/validators/network-options.tssrc/services/agent-volumes/etc-mounts.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/commands/validators/log-and-limits.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/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/services/api-proxy-service.tssrc/config-file.tssrc/rules.tssrc/compose-generator.tssrc/option-parsers.ts🔍 Notable Findings
src/commands/validators/network-options.ts— 66.7% stmt / 50% branch: The sole file in the "low" tier. As the validator for network CLI options (DNS, proxy, domain rules), the uncovered branches likely include error-handling paths for invalid domain lists or conflicting proxy flags. Worth adding negative-case tests.src/cli.ts— 85.7% stmt / 50% branch: The main orchestration entry point has half its branches uncovered. Given this file wires up all commands, the uncovered paths are probably signal handler edge cases and early-exit error flows. A small integration test covering--help, invalid arguments, and SIGINT simulation would help significantly.src/cli-options.ts— 93% stmt but only 25% function coverage: The 400-line options file has three-quarters of its exported functions never called in tests. These are likely option builder helpers that are exercised indirectly but not unit-tested directly. Consider checking whether the uncovered functions are dead code or need explicit tests.src/logs/audit-enricher.ts— 83.6% stmt / 74.1% branch (modified in the most recent commitfccd944): This file was updated to use agent-job runtime context. The coverage gap suggests the new code paths for loading context from a file may not be fully exercised — specifically the fallback and error branches added in that PR.📈 Recommendations
High —
src/cli.tsbranch coverage (50%): Add tests for error-handling and signal paths in the CLI entry point. Even a few targeted tests for--invalid-flag, missing required args, and interrupt handling would push branch coverage above 80%.High —
src/commands/validators/network-options.ts(66.7% stmt / 50% branch): Add negative-case unit tests: invalid domain format, empty domain list, conflicting--no-proxy/--allow-domainscombinations. This is a security validator — all rejection paths should be tested.Medium —
src/logs/audit-enricher.ts(83.6% / 74.1%): The file changed in the latest commit (Fix export-audit prompt generation to use agent-job runtime context #4128). Add tests for the new runtime context file loading paths, including the case where the file is missing or malformed.Low —
src/cli-options.tsfunction coverage (25%): Audit whether the 75% of uncovered functions are reachable. If they are live code, add direct unit tests; if they are dead code, consider removal.Generated by test-coverage-reporter workflow · Trigger:
push· Commit:fccd944Beta Was this translation helpful? Give feedback.
All reactions