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
#10143
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, but 89.47% branches.
cli.ts has the weakest security-adjacent branch coverage: 50% branch coverage, with statements at 85.71%.
Lowest-coverage files are outside the security-critical list:bounded-execution/finite-cardinality.ts (46.03% statements) and nvx/cleanup-registry.ts (48.21% statements) are the lowest in the report. Both are flagged CRITICAL in the gaps brief, but they are not in the security-critical set.
bounded-execution/finite-disclosure.ts has 11.42% branch coverage, the lowest branch figure in the report. Most of its conditional paths are untested.
Recent churn is concentrated in untested-looking areas: the last 7 days added resolved-config-artifact.ts helpers (file permissions, artifact ownership, output publishing) at 55.33% statement coverage.
🎯 Recommendations
High: Add tests for resolved-config-artifact.ts. This file has recent changes touching file permissions, artifact ownership (resolveArtifactOwner), and output publishing. Its 55.33% statement and 51.66% branch coverage leave the new write paths largely unverified. Prioritize writePrivateFile, openArtifactDirectory, and the publish functions.
High: Add branch tests for src/cli.ts. Branch coverage is 50%. Cover the untaken option and error-path branches in the orchestration flow. The file is on the security-critical list.
Medium: Raise domain-patterns.ts branch coverage from 89.47%. Two uncovered if branches and one switch branch were identified. Add tests for invalid and edge-case domain inputs, since this file validates ACL input.
Lower-priority follow-up: add tests for bounded-execution/finite-cardinality.ts and finite-disclosure.ts, which have the lowest statement and branch coverage in the report.
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, but 89.47% branches.cli.tshas the weakest security-adjacent branch coverage: 50% branch coverage, with statements at 85.71%.bounded-execution/finite-cardinality.ts(46.03% statements) andnvx/cleanup-registry.ts(48.21% statements) are the lowest in the report. Both are flagged CRITICAL in the gaps brief, but they are not in the security-critical set.bounded-execution/finite-disclosure.tshas 11.42% branch coverage, the lowest branch figure in the report. Most of its conditional paths are untested.resolved-config-artifact.tshelpers (file permissions, artifact ownership, output publishing) at 55.33% statement coverage.🎯 Recommendations
resolved-config-artifact.ts. This file has recent changes touching file permissions, artifact ownership (resolveArtifactOwner), and output publishing. Its 55.33% statement and 51.66% branch coverage leave the new write paths largely unverified. PrioritizewritePrivateFile,openArtifactDirectory, and the publish functions.src/cli.ts. Branch coverage is 50%. Cover the untaken option and error-path branches in the orchestration flow. The file is on the security-critical list.domain-patterns.tsbranch coverage from 89.47%. Two uncoveredifbranches and oneswitchbranch were identified. Add tests for invalid and edge-case domain inputs, since this file validates ACL input.Lower-priority follow-up: add tests for
bounded-execution/finite-cardinality.tsandfinite-disclosure.ts, which have the lowest statement and branch coverage in the report.Generated by test-coverage-reporter workflow. Trigger:
pushAll reactions