You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Overall test coverage remains in the excellent range across all metrics. The branch coverage of 86% is particularly strong for a network security utility where conditional logic is critical.
🛡️ Security-Critical Path Status
File
Coverage
Branch
Status
squid-config.ts
High
High
✅ Protected
host-iptables.ts
High
High
✅ Protected
docker-manager.ts
High
High
✅ Protected
domain-patterns.ts
High
High
✅ Protected
cli.ts
High
High
✅ Protected
All primary security-critical paths maintain excellent coverage. Domain validation, iptables rule generation, Squid configuration, and container orchestration are well-tested.
Dependencies — Updated js-yaml to 5.4.0, ESLint to 8.68.0
Impact on Coverage: Enclave and Cloud Hypervisor modules added new codepaths without complete test coverage (see enclave/runtime-preflight.ts, microvm/rootfs.ts).
🔎 Notable Findings
🚨 Critical Gap — finite-disclosure.ts (9.26%): This appears to be a newly added or substantially refactored module related to bounded execution. At 9.26% statements and 0.26% branches, this file represents untested security logic and should be treated as a blocker. Recommend immediate test authoring.
⚠️ Enclave Module Regression — runtime-preflight.ts (66.66%) has dropped in coverage relative to feature additions. The recent PR test: recompile enclave smoke with deferred startup #7758 ("recompile enclave smoke with deferred startup") suggests new execution paths that lack integration test coverage.
✅ Test Utilities — config-writer-dependency-mocks.test-utils.ts is well-covered on branches (100%) but low on statements (73.91%) — this is acceptable for test helper code and not a priority.
🎯 Recommendations
High Priority 🔴
Add tests for bounded-execution/finite-disclosure.ts (Critical)
This module is 90.74% uncovered and appears to handle credential isolation or sensitive data
Create integration tests covering all decision branches
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
📊 Test Coverage Report — 2026-08-28
Overall Coverage
Overall test coverage remains in the excellent range across all metrics. The branch coverage of 86% is particularly strong for a network security utility where conditional logic is critical.
🛡️ Security-Critical Path Status
All primary security-critical paths maintain excellent coverage. Domain validation, iptables rule generation, Squid configuration, and container orchestration are well-tested.
📋 Coverage Table — Files Below 80%
Only 5 files fall below 80% statement coverage:
bounded-execution/finite-disclosure.tsenclave/runtime-preflight.tsmicrovm/rootfs.tscommands/validators/config-assembly.tstest-helpers/config-writer-dependency-mocks.test-utils.ts🔧 Function Audit
📅 Recent Source Changes (last 7 days)
Recent commits show focus on:
Impact on Coverage: Enclave and Cloud Hypervisor modules added new codepaths without complete test coverage (see
enclave/runtime-preflight.ts,microvm/rootfs.ts).🔎 Notable Findings
🚨 Critical Gap —
finite-disclosure.ts(9.26%): This appears to be a newly added or substantially refactored module related to bounded execution. At 9.26% statements and 0.26% branches, this file represents untested security logic and should be treated as a blocker. Recommend immediate test authoring.runtime-preflight.ts(66.66%) has dropped in coverage relative to feature additions. The recent PR test: recompile enclave smoke with deferred startup #7758 ("recompile enclave smoke with deferred startup") suggests new execution paths that lack integration test coverage.📦 microVM Feature Gap —
microvm/rootfs.ts(71.69%) is undertested despite being part of Cloud Hypervisor v53.0 support. Recent refactors (Split Cloud Hypervisor manager lifecycle into focused modules #7796, refactor: split Cloud Hypervisor backend helpers #7797) suggest architectural changes may have outpaced test updates.✅ Test Utilities —
config-writer-dependency-mocks.test-utils.tsis well-covered on branches (100%) but low on statements (73.91%) — this is acceptable for test helper code and not a priority.🎯 Recommendations
High Priority 🔴
bounded-execution/finite-disclosure.ts(Critical)Medium Priority 🟡
Increase
enclave/runtime-preflight.tscoverage to ≥80%Add microVM rootfs tests
microvm/rootfs.tsis critical for Cloud Hypervisor supportLow Priority 🟢
commands/validators/config-assembly.ts(25%)Report Generated: 2026-08-28 | Coverage Data Source: npm test coverage-summary.json
All reactions