[Coverage Report] Test Coverage Report — 2026-05-22 #3589
Replies: 3 comments
-
|
🔮 The ancient spirits stir: the Codex smoke test agent passed through this chamber, leaving a clear sign in the workflow run. 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: the Codex smoke test agent was here, and its signal has passed through the veil of this workflow. 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... the smoke test agent was here, tracing green flame through the firewall runes. 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
🔴 Critical Gaps (< 50% statement coverage)
None — every source file is above 80% statement coverage.
🟡 Low Coverage (50–79% statement coverage)
None below 80%. The following are in the 80–86% range:
commands/validators/config-assembly.tscommands/validators/network-options.tslogs/audit-enricher.tslogs/log-parser.tsconfig-writer.tscli.ts🛡️ Security-Critical Path Status
host-iptables.tshost-iptables-rules.tshost-iptables-network.tshost-iptables-cleanup.tssquid-config.tssquid/domain-acl.tssquid/ssl-bump.tsdomain-patterns.tsdocker-manager.tsdlp.tsredact-secrets.tsAll security-critical paths exceed the 70% branch coverage threshold. 🎉
📋 Files Needing Attention (by branch coverage)
commands/validators/network-options.tscli-options.tscommands/validators/config-assembly.tslogs/log-parser.tsconfig-writer.tssquid/policy-manifest.ts🔍 Notable Findings
commands/validators/network-options.ts— 50% branch coverage: Network option validation (DNS servers, proxy settings, port configs) has half its branches untested. Missing coverage likely includes: invalid IP format rejection, conflicting option combinations, and edge values.cli-options.ts— 25% function coverage: Only 2 of 8 functions exercised. Uncovered functions likely handle option defaults, environment variable overrides, or deprecated flag paths — all worth testing as they control the firewall's runtime behaviour.logs/log-parser.ts— 65.6% branch coverage: Log parsing branches for malformed lines, missing fields, and alternate timestamp formats are not tested. These are real-world edge cases from production Squid logs.squid/policy-manifest.ts— 70% function coverage: 3 of 10 functions uncovered. Since this module feeds the Squid ACL generator, closing the gap would add defence-in-depth for the policy pipeline.📈 Recommendations
High —
commands/validators/network-options.tsbranch coverage (50%): Add tests for invalid DNS server IPs, conflicting proxy settings, and out-of-range ports. These validate security-relevant network configuration inputs.High —
cli-options.tsfunction coverage (25%): Write unit tests for each exported option-builder/resolver function. Uncovered option-parsing logic is a common source of subtle security misconfigurations.Medium —
logs/log-parser.tsbranch coverage (65.6%): Add tests with malformed Squid log lines, truncated entries, and non-standard timestamps to cover the defensive branches.Low —
squid/policy-manifest.tsfunction coverage (70%): Cover the remaining uncovered functions to bring this security-adjacent module to ≥95%.📊 Suite Statistics
ac64d63— remove unusedProbeResultexport)Generated by test-coverage-reporter workflow · Trigger:
push· 2026-05-22Beta Was this translation helpful? Give feedback.
All reactions