[Coverage Report] Test Coverage Report — 2026-05-12 #3032
Closed
Replies: 1 comment
-
|
This discussion was automatically closed because it expired on 2026-05-19T16:28:22.247Z.
|
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
🔴 Critical Gaps (< 50% statement coverage)
src/commands/main-action.ts🟡 Low Coverage (50–79% statement coverage)
src/commands/subcommands.tssrc/container-cleanup.ts🛡️ Security-Critical Path Status
src/host-iptables.tssrc/squid-config.tssrc/docker-manager.tssrc/domain-patterns.tssrc/cli.ts📋 Full Coverage Table
Per-file breakdown (click to expand)
commands/main-action.tscommands/subcommands.tscontainer-cleanup.tslogs/audit-enricher.tscli.tslogs/log-parser.tscommands/logs-command-helpers.tscli-workflow.tscontainer-lifecycle.tsservices/doh-proxy-service.tsservices/agent-volumes.tslogs/log-streamer.tscli-options.tsssl-bump.tslogs/log-aggregator.tsservices/cli-proxy-service.tsupstream-proxy.tspid-tracker.tssquid-config.tshost-iptables.tslogs/log-formatter.tsservices/agent-service.tsdomain-patterns.tsservices/agent-environment.tsconfig-file.tsrules.tshost-env.tscompose-generator.tsservices/api-proxy-service.tsoption-parsers.tsdocker-manager.tsapi-proxy-config.tscopilot-api-resolver.tsdlp.tsdns-resolver.tsdomain-utils.tsenv-utils.tsimage-tag.tslogger.tsredact-secrets.tsschema-validator.tscommands/logs-audit.tscommands/logs-stats.tscommands/logs-summary.tscommands/logs.tscommands/predownload.tslogs/index.tslogs/log-discovery.tslogs/stats-formatter.tsservices/squid-service.ts🔍 Notable Findings
commands/main-action.ts— newly added, 5.7% coverage: Added in the last 7 days,createMainAction()is the core CLI dispatch function but has almost no test coverage. Zero branch coverage means error paths, help handling, and config-load failures are completely untested.cli.ts— 50% branch coverage: The main entry point has full function coverage but only half of its conditional branches are exercised. Uncovered branches likely include error-handling paths (Docker daemon not running, permission errors, signal handling edge cases).commands/subcommands.ts— 21.4% branch coverage: Low branch coverage on subcommand routing means most command dispatch paths are untested. At 41.7% function coverage, more than half the functions have zero coverage.cli-options.ts— 25% function coverage: Three-quarters of option-parsing functions are uncovered, which could hide bugs in edge-case flag combinations (e.g., conflicting--enable-api-proxy+--build-localcombinations).📈 Recommendations
High: Add tests for
commands/main-action.ts— specifically forcreateMainAction()error paths (bad config, Docker unavailable, signal interrupts). Branch coverage is 0%; even basic happy-path + one error-path tests would dramatically improve it.High: Improve
cli.tsbranch coverage from 50% → 70%+. Focus on error branches: what happens whenstartContainers()fails mid-way, or when SIGTERM arrives during container startup.Medium: Add tests for
commands/subcommands.tscommand routing — especially the dispatch paths forlogs,predownload, and unknown subcommands.Low: Improve
cli-options.tsfunction coverage — parse the uncovered option-combination validation functions to ensure conflicting flags are rejected correctly.Generated by test-coverage-reporter workflow. Trigger:
pushBeta Was this translation helpful? Give feedback.
All reactions