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
[quality] src/main.ts entry point has no unit test (0% statements) #211
src/main.ts — the action's entry point (void run()) — is the only runtime source file left at 0% unit coverage that no open test PR claims.
Unit evidence, main @ 187c5e3: npm ci && npm run test:coverage → main.ts | 0 stmts | 100 branch | 100 funcs | 0 lines | uncovered: 3.
End-to-end evidence: the prow / prow check on every PR runs the built dist/index.js, which is main.ts bundled by ncc, so the entry point is exercised end-to-end (e.g. PR #188, job 108442385521, green). That check emits no coverage data, so this is unit-only evidence; the e2e claim rests on the bundle's import graph, not on a coverage report.
src/utils/context.ts also reports 0/0 but is type-only (a single export type), so it is not a gap.
Recommendation
Add __tests__/main.test.ts that mocks ../src/run, imports ../src/main, and asserts run was called exactly once with no arguments. Follows the existing vi.mock factory pattern in __tests__/run.test.ts.
Priority
Impact: low — covered end-to-end by the dogfood check; unit gap only
Activity
github-actions commentedon Sep 28, 2026
Please add a kind label with
/kind failing-testor/kind cleanup.test: cover the src/main.ts entry point (#212)