[Coverage Report] Test Coverage Report — 2026-08-20 #7571
Closed
Replies: 1 comment
|
This discussion was automatically closed because it expired on 2026-08-27T18:45:50.146Z.
|
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.
📊 Test Coverage Report — 2026-08-20
Overall Coverage
Status: Project maintains strong coverage overall (>92% statements), but critical security gaps exist in new bounded-execution features.
🛡️ Security-Critical Path Status
Core firewall modules are well-tested. New bounded-execution and cloud-hypervisor paths have significant gaps.
📋 Coverage Table — Top 10 Lowest Coverage Files
🔧 Function Audit
Functions with 0% coverage:
finite-disclosure.ts: 42 of 44 functions untested (95% gap in function count alone)virtiofsd.ts: 10 of 19 functions untested (function coverage: 47.36%)config-assembly.ts: Only 1 function defined; logic gaps suggest untested branchesBranch coverage gaps indicate:
📅 Recent Source Changes (last 7 days)
Pre-computed data indicates these files were modified recently:
src/bounded-execution/finite-disclosure.ts— new feature for bounded executionsrc/enclave/runtime-preflight.ts— new enclave validation pathssrc/cloud-hypervisor/virtiofsd.ts— cloud-hypervisor integrationsrc/microvm/rootfs.ts— microVM filesystem setupObservation: New features added without corresponding test coverage.
🔎 Notable Findings
Critical Gap: bounded-execution/finite-disclosure.ts at 9.26%
Branch Coverage Regression in New Features
Core Firewall Modules Remain Strong
cli.ts Entry Point at 85.71%
🎯 Recommendations
🔴 HIGH PRIORITY
🟡 MEDIUM PRIORITY
Improve branch coverage in config-assembly.ts and runtime-preflight.ts
Add signal handling tests to cli.ts
SIGTERM/SIGINTsignals🟢 LOW PRIORITY
Report generated: 2026-08-20
Coverage tool: NYC (Istanbul)
Test framework: Jest
All reactions