[Coverage Report] Test Coverage Report — 2026-05-19 #3399
Closed
Replies: 1 comment
-
|
This discussion was automatically closed because it expired on 2026-05-26T05:53:13.974Z.
|
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.
-
Overall Coverage
72 test files covering 101 source files
🔴 Critical Gaps (< 50% statement coverage)
None — all files are above 50%.
🟡 Low Coverage (50–79% statement coverage)
src/commands/build-config.ts🛡️ Security-Critical Path Status
src/host-iptables.tssrc/squid-config.tssrc/docker-manager.tssrc/domain-patterns.tssrc/cli.tsAll five security-critical files are well-covered.
cli.tsbranch coverage at 50% is the only security-adjacent gap.📋 Full Coverage Table
All files (click to expand)
src/commands/build-config.tssrc/commands/main-action.tssrc/logs/audit-enricher.tssrc/commands/predownload.tssrc/logs/log-parser.tssrc/config-writer.tssrc/cli.tssrc/commands/validate-options.tssrc/squid/policy-manifest.tssrc/commands/logs-command-helpers.tssrc/cli-workflow.tssrc/services/host-path-prefix.tssrc/services/doh-proxy-service.tssrc/container-cleanup.tssrc/host-iptables-shared.tssrc/services/agent-volumes.tssrc/logs/log-streamer.tssrc/cli-options.tssrc/squid/ssl-bump.tssrc/ssl-bump.tssrc/container-lifecycle.tssrc/logs/log-aggregator.tssrc/upstream-proxy.tssrc/services/cli-proxy-service.tssrc/host-env.tssrc/parsers/volume-parsers.tssrc/pid-tracker.tssrc/host-iptables-rules.tssrc/logs/log-formatter.tssrc/domain-patterns.tssrc/services/agent-service.tssrc/services/agent-environment.tssrc/config-file.tssrc/rules.tssrc/compose-generator.tssrc/services/api-proxy-service.tssrc/option-parsers.tssrc/api-proxy-config.tssrc/docker-manager.tssrc/host-iptables.tssrc/squid-config.tssrc/domain-patterns.ts🔍 Notable Findings
src/commands/build-config.ts(50% stmts, 0% branches/functions) — Added recently as part of CLI refactoring, this config-assembly module has no dedicated tests. ThebuildConfig()function handles credential resolution (resolveCopilotApiKey) and constructsWrapperConfig, making untested branches a potential source of misconfiguration bugs.src/cli.tsbranch coverage at 50% — All functions are covered but half the conditional branches are not exercised. Error-handling paths (e.g., signal handling, partial startup failures) are the most likely gaps.src/commands/predownload.ts(85% stmts, 61% branches) — Pre-image-download logic has uncovered branch paths. Combined with thebuild-config.tsgap, startup-path error handling is the weakest area in the codebase.src/cli-options.ts(93% stmts, 60% branches, 25% functions) — Only 1 of 4 exported functions is covered. Option-parsing edge cases (invalid input, defaults) are not tested.📈 Recommendations
High — Add tests for
src/commands/build-config.ts: Write unit tests forbuildConfig()covering: valid inputs produce correctWrapperConfig;resolveCopilotApiKeyerror propagation; optional fields (memoryLimit,agentImage,modelAliases) handled correctly. This brings a 0%-function file up to coverage and closes a config correctness gap.Medium — Cover
src/cli.tsbranch gaps: Add tests for the untested conditional branches — most likely the SIGINT/SIGTERM handler,--keep-containersearly exit path, and startup-failure cleanup. This improves branch coverage from 50% → ~85%.Low — Expand
src/cli-options.tsfunction coverage: Three of four exported functions are untested. Add tests for the uncovered option-parsing helpers to guard against regressions when new CLI flags are added.Generated by test-coverage-reporter workflow. Trigger:
scheduleBeta Was this translation helpful? Give feedback.
All reactions