[Coverage Report] Test Coverage Report — 2026-09-24 #8946
Replies: 3 comments
|
🔮 The ancient spirits stir, and the oracle records this passage: the smoke test agent walked here, saw the signs align, and left the wards intact. Warning Firewall blocked 13 domainsThe following domains were blocked by the firewall during workflow execution:
[!TIP] tools:
github:
mode: gh-proxySee GitHub Tools for more information on To allow these domains, add them to the network:
allowed:
- defaults
- "ab.chatgpt.com"
- "accounts.google.com"
- "android.clients.google.com"
- "api.github.com"
- "clients2.google.com"
- "collector.github.com"
- "contentautofill.googleapis.com"
- "github.com"
- "github.githubassets.com"
- "msfeed25.pkgs.visualstudio.com"
- "update.googleapis.com"
- "www.google.com"
- "www.gstatic.com"See Network Configuration for more information.
|
|
🔮 The ancient spirits stir, and the smoke-test agent has walked this thread. The omens are clear: the checks passed, the build held, and the fire remains contained. Warning Firewall blocked 13 domainsThe following domains were blocked by the firewall during workflow execution:
[!TIP] tools:
github:
mode: gh-proxySee GitHub Tools for more information on To allow these domains, add them to the network:
allowed:
- defaults
- "ab.chatgpt.com"
- "accounts.google.com"
- "android.clients.google.com"
- "api.github.com"
- "clients2.google.com"
- "collector.github.com"
- "contentautofill.googleapis.com"
- "github.com"
- "github.githubassets.com"
- "msfeed25.pkgs.visualstudio.com"
- "update.googleapis.com"
- "www.google.com"
- "www.gstatic.com"See Network Configuration for more information.
|
|
🔮 The ancient spirits stir, and the smoke test agent was here. Warning Firewall blocked 12 domainsThe following domains were blocked by the firewall during workflow execution:
[!TIP] tools:
github:
mode: gh-proxySee GitHub Tools for more information on To allow these domains, add them to the network:
allowed:
- defaults
- "ab.chatgpt.com"
- "accounts.google.com"
- "api.github.com"
- "clients2.google.com"
- "collector.github.com"
- "contentautofill.googleapis.com"
- "github.com"
- "github.githubassets.com"
- "msfeed25.pkgs.visualstudio.com"
- "update.googleapis.com"
- "www.google.com"
- "www.gstatic.com"See Network Configuration for more information.
|
Uh oh!
There was an error while loading. Please reload this page.
Overall Coverage
Global Coverage Metrics:
Test Suite Results:
🛡️ Security-Critical Path Status
The security-critical modules maintain strong coverage overall, but three new modules show significant gaps requiring attention:
New/Growing Modules with Coverage Gaps:
📋 Coverage Table
Top Module Coverage (>95%):
Modules with Branch Coverage Gaps (>10% gap between stmt/branch):
🔧 Function Audit
Functions with Low Statement Coverage in Critical Modules:
src/nvx/cleanup-registry.ts (42.8% stmt / 32.1% branch)
src/bounded-execution/finite-cardinality.ts (46.0% stmt / 35.3% branch)
src/bounded-execution/finite-schema.ts (49.3% stmt / 42.7% branch)
src/logging-assembly.ts (80.39% stmt / 47.61% branch)
📅 Recent Source Changes (last 7 days)
The following security-critical modules were recently modified or have active test coverage improvements:
src/nvx/— Full test suite present; tests PASSINGsrc/bounded-execution/— New module; test suites in progresssrc/microvm/— Comprehensive testing; 86.6% statement coveragesrc/logs/— Mature module; 98.65% statement coverage🔎 Notable Findings
Security Coverage Stable — All legacy security-critical paths (squid config, host iptables, domain patterns) maintain 100% coverage across all metrics. No regression.
New Bounded Execution Module Under-Tested — Three new modules in
src/bounded-execution/show critical coverage gaps (42–49% statements, 11–43% branches). These modules appear to implement new security-relevant features that need comprehensive test coverage before production use.Branch Coverage Gaps — Five files show >10% gap between statement and branch coverage, indicating conditional logic is under-tested. Most critical:
src/bounded-execution/finite-disclosure.ts(40.36% gap).Test Failures Unrelated to Coverage — Four failing tests are schema/catalog sync issues (not coverage-related):
api-proxy-env-config.test.ts: OTEL_SERVICE_NAME mismatchschema.test.ts: Anthropic domain pattern schema mismatchclaude-hosted-web-policy.test.ts: Schema sync failurecopilot-model-catalog-sync.test.ts: Missing gpt-6-* models🎯 Recommendations
HIGH Priority:
src/bounded-execution/finite-*.tsmodulesMEDIUM Priority:
2. Reduce branch coverage gaps in existing modules
src/logging-assembly.ts(47.61% branch coverage)LOW Priority:
3. Resolve test failures and schema mismatches
Report Generated: 2026-09-24
Coverage Tool: Jest + Istanbul
Data Source: Pre-computed test run
All reactions