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-21
#10429
Note: the per-function audit for host-iptables.ts and squid-config.ts returned no entries, so it does not confirm function-level coverage for those files. The file-level metrics above show 100%.
📅 Recent Source Changes (last 7 days)
src/agent-entrypoint-gemini-settings.test.ts
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
---
+export function isRouterOtelHostEnvVar(name: string): boolean {
+export function buildRouterOtelEnv(hostEnv: NodeJS.ProcessEnv): Record<string, string> {
+export function redactOtlpEnvValue(name: string, value: unknown): unknown {
+export function buildRouterService({ imageConfig, hostEnv = process.env }: RouterServiceParams): any {
+export function createPrimaryReadinessReporter(directory: string) {
+export function createDockerHostEnclaveExecutor(options: DockerHostEnclaveExecutorOptions): DockerHostEnclaveExecutorBackend {
+export async function recoverDockerHostEnclaveExecutor(
+export function captureDockerHostOwner(): DockerHostOwnerIdentity {
+export function assertDockerHostOwnerStopped(owner: DockerHostOwnerIdentity | undefined, current: DockerHostOwnerIdentity): void {
+export function expectedDockerHostContainer(args: readonly string[]): DockerHostExpectedContainer {
🔎 Notable Findings
Security-critical files are fully covered.host-iptables.ts, squid-config.ts, docker-manager.ts, and domain-patterns.ts are at 100% statements and functions. The only weak spot is branch coverage in domain-patterns.ts (89.47%) and cli.ts (50%).
src/cli.ts has the lowest branch coverage among critical paths at 50%, despite 87.5% statements. Its untested branches are in the orchestration entry point.
Three files are critically low (under 50% statements): bounded-execution/finite-cardinality.ts, resolved-config-artifact.ts, and nvx/cleanup-registry.ts. None are on the security-critical list, but cleanup-registry.ts manages resource teardown, so gaps there could leave resources behind.
bounded-execution/finite-disclosure.ts has 11.42% branch coverage, the lowest branch figure in the report.
Recent changes add new exported functions in docker-manager-adjacent enclave code (for example createDockerHostEnclaveExecutor, recoverDockerHostEnclaveExecutor, assertDockerHostOwnerStopped). These are new public surface and should have direct tests.
🎯 Recommendations
High: Add branch tests for src/cli.ts. It is the main entry point and sits at 50% branch coverage. Cover the error and flag-combination paths in orchestration.
High: Add tests for src/nvx/cleanup-registry.ts and src/resolved-config-artifact.ts. Both are under 50% statements. Prioritize cleanup and teardown paths to prevent leaked resources.
Medium: Test the new enclave Docker-host functions (createDockerHostEnclaveExecutor, recoverDockerHostEnclaveExecutor, assertDockerHostOwnerStopped, captureDockerHostOwner). They are recent additions with no visible direct coverage in this report.
Low: Raise branch coverage in src/bounded-execution/finite-disclosure.ts (11.42%) and src/domain-patterns.ts (89.47%, the remaining branches of its two if statements and one switch).
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-21
Overall Coverage
🛡️ Security-Critical Path Status
📋 Coverage Table
🔧 Function Audit
Note: the per-function audit for
host-iptables.tsandsquid-config.tsreturned no entries, so it does not confirm function-level coverage for those files. The file-level metrics above show 100%.📅 Recent Source Changes (last 7 days)
🔎 Notable Findings
host-iptables.ts,squid-config.ts,docker-manager.ts, anddomain-patterns.tsare at 100% statements and functions. The only weak spot is branch coverage indomain-patterns.ts(89.47%) andcli.ts(50%).src/cli.tshas the lowest branch coverage among critical paths at 50%, despite 87.5% statements. Its untested branches are in the orchestration entry point.bounded-execution/finite-cardinality.ts,resolved-config-artifact.ts, andnvx/cleanup-registry.ts. None are on the security-critical list, butcleanup-registry.tsmanages resource teardown, so gaps there could leave resources behind.bounded-execution/finite-disclosure.tshas 11.42% branch coverage, the lowest branch figure in the report.docker-manager-adjacent enclave code (for examplecreateDockerHostEnclaveExecutor,recoverDockerHostEnclaveExecutor,assertDockerHostOwnerStopped). These are new public surface and should have direct tests.🎯 Recommendations
src/cli.ts. It is the main entry point and sits at 50% branch coverage. Cover the error and flag-combination paths in orchestration.src/nvx/cleanup-registry.tsandsrc/resolved-config-artifact.ts. Both are under 50% statements. Prioritize cleanup and teardown paths to prevent leaked resources.createDockerHostEnclaveExecutor,recoverDockerHostEnclaveExecutor,assertDockerHostOwnerStopped,captureDockerHostOwner). They are recent additions with no visible direct coverage in this report.src/bounded-execution/finite-disclosure.ts(11.42%) andsrc/domain-patterns.ts(89.47%, the remaining branches of its twoifstatements and oneswitch).All reactions