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-16
#10134
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 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 {
+export function publishFinalResolvedConfig(directory: string, contents: string): void {
+export function publishEarlyResolvedConfig(contents: string): string {
+export function exportResolvedConfigPath(file: string): void {
🔎 Notable Findings
Security-critical files are fully covered.host-iptables.ts, squid-config.ts, and docker-manager.ts are at 100% on statements, branches, and functions. domain-patterns.ts is at 100% statements and functions, with 89.47% branch coverage.
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) are the largest gaps.
src/bounded-execution/finite-disclosure.ts has very low branch coverage at 11.42%, despite 51.78% statement coverage. Most of its decision paths are untested.
src/cli.ts branch coverage is 50%. Statements and functions are good, but half the conditional paths in the main entry point are untested.
Recent churn is in under-tested code. The last 7 days added or changed bounded-execution schema serialization, resolved-config-artifact publishing, and gateway readiness code, which are all in the low-coverage set above.
🎯 Recommendations
High: Add tests for src/bounded-execution/finite-cardinality.ts and src/nvx/cleanup-registry.ts. Both are below 50% statement coverage. Cover the error and boundary branches first, since these are the two lowest-coverage files.
Medium: Cover the branches in src/cli.ts and src/bounded-execution/finite-disclosure.ts. Add tests for the untested if and switch paths in cli.ts. In finite-disclosure.ts, add cases for each decision path, since branch coverage is 11.42%.
Low: Raise src/resolved-config-artifact.ts and the 2026-10 src/microvm/ files above 70%. Focus on the newly exported publish*ResolvedConfig and openArtifactDirectory functions, which are recent additions without matching coverage.
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-16
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% on statements, branches, and functions.domain-patterns.tsis at 100% statements and functions, with 89.47% branch coverage.src/bounded-execution/finite-cardinality.ts(46.03% statements, 35.29% branches) andsrc/nvx/cleanup-registry.ts(48.21% statements, 38.53% branches) are the largest gaps.src/bounded-execution/finite-disclosure.tshas very low branch coverage at 11.42%, despite 51.78% statement coverage. Most of its decision paths are untested.src/cli.tsbranch coverage is 50%. Statements and functions are good, but half the conditional paths in the main entry point are untested.bounded-executionschema serialization,resolved-config-artifactpublishing, and gateway readiness code, which are all in the low-coverage set above.🎯 Recommendations
src/bounded-execution/finite-cardinality.tsandsrc/nvx/cleanup-registry.ts. Both are below 50% statement coverage. Cover the error and boundary branches first, since these are the two lowest-coverage files.src/cli.tsandsrc/bounded-execution/finite-disclosure.ts. Add tests for the untestedifandswitchpaths incli.ts. Infinite-disclosure.ts, add cases for each decision path, since branch coverage is 11.42%.src/resolved-config-artifact.tsand the 2026-10src/microvm/files above 70%. Focus on the newly exportedpublish*ResolvedConfigandopenArtifactDirectoryfunctions, which are recent additions without matching coverage.Generated by test-coverage-reporter workflow. Trigger:
pushAll reactions