[Coverage Report] ๐ Test Coverage Report โ 2026-09-10 #8417
Closed
Replies: 2 comments
|
This discussion was automatically closed because it expired on 2026-09-17T20:06:29.289Z.
|
0 replies
|
๐ฎ The ancient spirits stir. A smoke-test envoy passed through this chamber, and the omens held true. 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.
|
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.
Overall Coverage
Current Project-Wide Coverage Metrics:
Overall coverage is healthy across all metrics. Branch coverage (86.61%) is the lowest area and represents the primary improvement opportunity.
๐ก๏ธ Security-Critical Path Status
The security-critical firewall paths have excellent coverage:
src/host-iptables.tssrc/squid-config.tssrc/docker-manager.tssrc/domain-patterns.tssrc/cli.tssrc/cli.tshas 50% branch coverage โ a split code path in the CLI wrapper is not exercised by the test suite. This should be addressed.๐ Coverage Table โ Critical Gaps
src/bounded-execution/finite-disclosure.tssrc/microvm/network-reservation.tssrc/enclave/runtime-preflight.tssrc/microvm/rootfs.tssrc/commands/validators/config-assembly.tsRecommendation: Focus first on
finite-disclosure.ts(CRITICAL) as it governs output bounds. microVM network reservation is also high-priority for sandbox isolation.๐ง Function Audit
Key low-coverage functions require investigation:
src/bounded-execution/finite-disclosure.ts(38.12% statements)src/microvm/network-reservation.ts(50.22% statements)src/cli.ts(50% branch coverage)๐ Recent Source Changes (last 7 days)
Recent commits touching the firewall codebase:
407226fโ Add--network-subnetto relocate awf-net off colliding host/cluster subnets (Add --network-subnet to relocate awf-net off colliding host/cluster subnetsย #8398)a8ce656โ Support Codex apply_patch through Copilot Responses API (Support Codex apply_patch through Copilot Responses APIย #8359)9e89ccaโ Refactor provider adapter registration (Refactor provider adapter registrationย #8335)f895fcaโ Refactor: centralize agent sandbox path policy (refactor: centralize agent sandbox path policyย #8334)e015efdโ Test: add end-to-end security coverage for dynamic repository enclaves (test: add end-to-end security coverage for dynamic repository enclavesย #8307)Key observation: Recent changes are mostly refactoring and configuration. The
--network-subnetchange should be covered by existing network tests.๐ Notable Findings
Security boundary exposure:
finite-disclosure.ts(38.12%) is a CRITICAL gap โ output bounds enforcement is the last line of defense against data exfiltration. This must be addressed.microVM isolation risk:
network-reservation.tsat 50.22% means half of the network isolation code is untested. Given microVM is a preview feature, this should be remediated before GA.CLI edge cases: The 50% branch coverage in
src/cli.tssuggests signal handling or error conditions are missing test cases โ these are often security-relevant paths.Overall health: Project-wide coverage is strong (92.76% statements, 94.09% lines), but branch coverage (86.61%) lags โ this indicates missing conditional paths in happy-path tests.
๐ฏ Recommendations
Priority 1 (CRITICAL):
src/bounded-execution/finite-disclosure.tsPriority 2 (HIGH):
src/microvm/network-reservation.tsPriority 3 (MEDIUM):
src/cli.tsAll reactions