Repository navigation
[Coverage Report] Test Coverage Report — 2026-10-16 #10059
Replies: 1 comment
|
🔮 The ancient spirits stir, and the oracle marks this hall: the smoke test agent was here. May the signals remain true and the paths unbroken.
|
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Overall Coverage
🛡️ Security-Critical Path Status
📋 Coverage Table
🔧 Function Audit
📅 Recent Source Changes (last 7 days)
New exported functions in the same window:
🔎 Notable Findings
host-iptables.ts,squid-config.ts, anddocker-manager.tsare at 100% across statements, branches, and functions.domain-patterns.tsis at 100% statements but 89.47% branches.src/bounded-execution/finite-cardinality.ts(46.03% statements, 35.29% branches) andsrc/nvx/cleanup-registry.ts(48.21% statements, 38.53% branches).src/bounded-execution/finite-disclosure.tsis at 11.42% branches, andsrc/cli.tsat 50% branches.resolved-config-artifactand enclave-debug paths. Several new functions (publishFinalResolvedConfig,validatePublicEnclaveDebug,githubTokenEnvNames) have low file-level coverage insrc/resolved-config-artifact.ts(55.33% statements).🎯 Recommendations
src/bounded-execution/finite-cardinality.tsandsrc/nvx/cleanup-registry.ts. Both are below 50% statements. Prioritize the branch paths, since branch coverage is 35–38%.src/resolved-config-artifact.ts. TargetpublishFinalResolvedConfig,publishEarlyResolvedConfig,assertPersistentDebugArtifactsIsolated, andvalidatePublicEnclaveDebug, including their rejection paths.src/domain-patterns.ts(89.47%) andsrc/cli.ts(50%). These are security-adjacent, so add tests for the uncoveredif/switcharms, starting with domain validation edge cases.Generated by test-coverage-reporter workflow. Trigger:
pushAll reactions