[Coverage Report] 📊 Test Coverage Report — 2026-09-16 #8658
Replies: 3 comments
|
🔮 The ancient spirits stir, and the smoke test agent has walked this hall. Warning Firewall blocked 8 domainsThe following domains were blocked by the firewall during workflow execution:
To allow these domains, add them to the network:
allowed:
- defaults
- "accounts.google.com"
- "android.clients.google.com"
- "clients2.google.com"
- "contentautofill.googleapis.com"
- "msfeed25.pkgs.visualstudio.com"
- "update.googleapis.com"
- "www.google.com"
- "www.gstatic.com"See Network Configuration for more information.
|
Oracle Sign🔮 The ancient spirits stir over this discussion. The smoke test agent passed through, read the signs, and marked this thread beneath a clear sky. Warning Firewall blocked 7 domainsThe following domains were blocked by the firewall during workflow execution:
To allow these domains, add them to the network:
allowed:
- defaults
- "accounts.google.com"
- "clients2.google.com"
- "contentautofill.googleapis.com"
- "msfeed25.pkgs.visualstudio.com"
- "update.googleapis.com"
- "www.google.com"
- "www.gstatic.com"See Network Configuration for more information.
|
|
This discussion was automatically closed because it expired on 2026-09-23T20:22:30.994Z.
|
Uh oh!
There was an error while loading. Please reload this page.
Overall Coverage
Status: Overall coverage is healthy at 92–94% across all primary metrics. Branch coverage (86.6%) is the lowest, reflecting untested error paths and edge conditions.
🛡️ Security-Critical Path Status
The following files contain network isolation and domain filtering logic critical to firewall security:
src/host-iptables.tssrc/squid-config.tssrc/docker-manager.tssrc/domain-patterns.tssrc/bounded-execution/finite-disclosure.tssrc/enclave/runtime-preflight.tsKey Finding: Core firewall rules (
host-iptables.ts,squid-config.ts,domain-patterns.ts) are well-tested. However, bounded execution disclosure isolation (finite-disclosure.ts) has severe coverage gaps at only 38% statements and 26% branches—this is a critical security-sensitive area requiring attention.📋 Coverage Table (Lowest 10 Files)
bounded-execution/finite-disclosure.tsmicrovm/network-reservation.tsenclave/runtime-preflight.tsmicrovm/rootfs.tstest-helpers/config-writer-dependency-mocks.test-utils.ts🔧 Function Audit
Full Coverage (100%):
src/host-iptables.ts— 3/3 functionssrc/squid-config.ts— 2/2 functionssrc/docker-manager.ts— 15/15 functionssrc/domain-patterns.ts— 3/3 functionssrc/enclave/runtime-preflight.ts— 5/5 functionssrc/microvm/rootfs.ts— 6/6 functionsGaps:
src/bounded-execution/finite-disclosure.ts— 26/47 functions tested (55.31%) — missing disclosure limit enforcement and repository staging pathssrc/microvm/network-reservation.ts— 25/44 functions tested (56.81%) — missing network isolation reservation logic📅 Recent Source Changes (Last 7 Days)
Recent commits indicate active maintenance and feature development:
These changes touch networking, API proxy, and enclave workflows—areas where test coverage ensures safe deployment.
🔎 Notable Findings
Bounded Execution Disclosure Isolation is Under-Tested (38% statements)
MicroVM Network Reservation Logic Needs Test Depth (50% statements)
Enclave Runtime Preflight Validation is Partially Covered (67% statements, 41% branches)
Domain Filtering Logic is Robust ✅
domain-patterns.ts(100% statements) and Squid config (100%) ensure domain allowlist enforcement is fully tested.🎯 Recommendations
1. 🔴 HIGH PRIORITY — Test Bounded Execution Disclosure Isolation
src/bounded-execution/finite-disclosure.ts2. 🟡 MEDIUM PRIORITY — Validate MicroVM Network Reservation Logic
src/microvm/network-reservation.tsedge cases and network isolation scenarios3. 🟡 MEDIUM PRIORITY — Complete Enclave Runtime Preflight Test Coverage
src/enclave/runtime-preflight.tsNext Steps:
All reactions