[Coverage Report] 📊 Test Coverage Report — 2026-09-17 #8689
Replies: 4 comments
|
🔮 The ancient spirits stir, and the smoke has been read. 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.
|
|
🔮 The ancient spirits stir. The smoke-test agent was here, read the signs, and left this mark in the ledger. Warning Firewall blocked 1 domainThe following domain was blocked by the firewall during workflow execution:
To allow these domains, add them to the network:
allowed:
- defaults
- "msfeed25.pkgs.visualstudio.com"See Network Configuration for more information.
|
|
🔮 The ancient spirits stir, and the smoke-test agent has passed this way. 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"
- "android.clients.google.com"
- "clients2.google.com"
- "contentautofill.googleapis.com"
- "msfeed25.pkgs.visualstudio.com"
- "www.google.com"
- "www.gstatic.com"See Network Configuration for more information.
|
|
This discussion was automatically closed because it expired on 2026-09-24T04:41:54.403Z.
|
Uh oh!
There was an error while loading. Please reload this page.
Overall Coverage
Assessment: Strong overall coverage with all metrics above 86%. Most of the codebase has excellent test support. ✅
🛡️ Security-Critical Path Status
Key Finding: Core network isolation (
host-iptables-*) and domain filtering (squid-config,domain-patterns) are fully covered. This is excellent for security-critical code. The main entry point (cli.ts) has gaps, but it's largely a wrapper around well-tested modules.📋 Coverage Table
Top Coverage (95-100%)
Moderate Coverage (80-95%)
Low Coverage (<80%)
src/bounded-execution/finite-disclosure.tssrc/microvm/network-reservation.tssrc/enclave/runtime-preflight.tssrc/microvm/rootfs.tssrc/test-helpers/config-writer-dependency-mocks.test-utils.ts🔧 Function Audit
Fully Tested Functions
setupIptablesChain()— 100% coverage, critical for network namespace setupgenerateSquidConfig()— 100% coverage, generates ACL rulesgetDockerComposePath()— 100% coverage, container orchestrationvalidateDomainPattern()— 100% coverage, domain whitelistingcalculateCapabilities()— 100% coverage, capability filteringPartially Tested Functions
cli.tsentry point — 85.71% statements, 50% branches📅 Recent Source Changes (last 7 days)
Recent commits suggest focus on:
Observation: New features in
src/cloud-hypervisor/andsrc/enclave/added complexity, with coverage still ramping. This is expected for newer modules.🔎 Notable Findings
🛡️ Network Isolation is Rock-Solid
host-iptables-*.tsfiles at 100% coveragesquid-config.ts,domain-patterns.ts) fully testedsrc/bounded-execution/finite-disclosure.tsat 38.12% (CRITICAL)src/microvm/rootfs.tsat 71.69%src/enclave/runtime-preflight.tsat 68.42%🎯 Entry Point Gaps
cli.tshas 50% branch coverage — some error/recovery paths untested📊 No Regression
🎯 Recommendations
High Priority
src/bounded-execution/finite-disclosure.ts(currently 38.12% statements)Medium Priority
Improve branch coverage for
cli.tserror paths (currently 50%)Expand
src/microvm/rootfs.tstests (currently 71.69%)Low Priority
src/enclave/runtime-preflight.tsat 68.42% — acceptable for new codeAll reactions