You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Coverage Report] Test Coverage Report — 2026-10-17
#10172
src/agent-entrypoint-output.test.ts
src/agent-helper-staging.test.ts
src/agent-runtime-start.test.ts
src/agent-runtime-start.ts
src/api-proxy-config-domains.test.ts
src/api-proxy-config-domains.ts
src/api-proxy-config-validation.test.ts
src/api-proxy-config-validation.ts
src/api-proxy-config-warnings.test.ts
src/api-proxy-config-warnings.ts
---
+export const ENCLAVE_ARTIFACT_VERIFICATION_STORAGE_PROFILE = Object.freeze({
+export function prepareTrustedArtifactVerificationStorage(
+export function handoffPrivateEnclaveAudit(
+export function serializeFiniteSchema(schema: FiniteSchemaNode): FiniteSchemaWireNode {
+export const HOST_EXECUTOR_REJECTION_STAGES = Object.freeze([
+export function readGatewayReadinessResponse(
+export function requireObject(
+export async function writePrivateFile(
+export function resolveArtifactOwner(): { uid: number; gid: number } {
+export function openArtifactDirectory(directory: string): number {
🔎 Notable Findings
Security-critical files are fully covered on statements and functions.host-iptables.ts, squid-config.ts, and docker-manager.ts are at 100%. domain-patterns.ts is at 100% statements but 89.47% branches (2 if-branches and 1 switch-branch are untested).
Two files are critically low:src/bounded-execution/finite-cardinality.ts (46.03% statements, 35.29% branches) and src/nvx/cleanup-registry.ts (48.21% statements, 38.53% branches). Neither is on the security-critical list.
src/cli.ts has 50% branch coverage despite 85.71% statement coverage. It is the orchestration entry point, so its untested branches sit on the main control flow.
src/bounded-execution/finite-disclosure.ts has 11.42% branch coverage, the lowest branch figure in the report, with 37.5% function coverage.
🎯 Recommendations
High: Add tests for src/bounded-execution/finite-cardinality.ts and src/nvx/cleanup-registry.ts. Both are below 50% statements. Cover the error and cleanup paths first, since untested cleanup code is where resource leaks hide.
Medium: Add branch tests for src/cli.ts and src/domain-patterns.ts. Target the 50% branch figure in cli.ts and the 2 untested if branches plus 1 switch branch in domain-patterns.ts. Those branches govern domain validation and entry-point behavior.
Low: Raise src/bounded-execution/finite-disclosure.ts (11.42% branch) and the 50–60% files (src/microvm/network-reservation.ts, src/resolved-config-artifact.ts) when those modules next change. Prioritize finite-disclosure.ts, which has the lowest branch figure.
Generated by test-coverage-reporter workflow. Trigger: push
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
📊 Test Coverage Report — 2026-10-17
Overall Coverage
🛡️ Security-Critical Path Status
📋 Coverage Table
🔧 Function Audit
📅 Recent Source Changes (last 7 days)
🔎 Notable Findings
host-iptables.ts,squid-config.ts, anddocker-manager.tsare at 100%.domain-patterns.tsis at 100% statements but 89.47% branches (2 if-branches and 1 switch-branch are untested).src/bounded-execution/finite-cardinality.ts(46.03% statements, 35.29% branches) andsrc/nvx/cleanup-registry.ts(48.21% statements, 38.53% branches). Neither is on the security-critical list.src/cli.tshas 50% branch coverage despite 85.71% statement coverage. It is the orchestration entry point, so its untested branches sit on the main control flow.src/bounded-execution/finite-disclosure.tshas 11.42% branch coverage, the lowest branch figure in the report, with 37.5% function coverage.🎯 Recommendations
src/bounded-execution/finite-cardinality.tsandsrc/nvx/cleanup-registry.ts. Both are below 50% statements. Cover the error and cleanup paths first, since untested cleanup code is where resource leaks hide.src/cli.tsandsrc/domain-patterns.ts. Target the 50% branch figure incli.tsand the 2 untestedifbranches plus 1switchbranch indomain-patterns.ts. Those branches govern domain validation and entry-point behavior.src/bounded-execution/finite-disclosure.ts(11.42% branch) and the 50–60% files (src/microvm/network-reservation.ts,src/resolved-config-artifact.ts) when those modules next change. Prioritizefinite-disclosure.ts, which has the lowest branch figure.Generated by test-coverage-reporter workflow. Trigger:
pushAll reactions