Project Test Coverage Review

[dligthart]

Test Coverage Review

I've reviewed the current test coverage for the WordClaw project using vitest run --coverage.

Current Overall Coverage

• Statements: 36.71%
• Branches: 27.63%
• Functions: 43.69%
• Lines: 37.31%

While the core functionality and many edge cases in the GraphQL layer and contracts are well-tested, there are several key files and areas where coverage is significantly lacking or non-existent.

Critical Areas Needing Improvement

Below are the modules with the lowest coverage (under 25%) that should be prioritized for testing:

1. Core Services & Licensing

• src/services/licensing.ts (0% coverage)
• src/services/mock-payment-provider.ts (0% coverage)
• src/services/payment-ledger.ts (9.09% coverage)
• src/services/webhook.ts (6.06% coverage)
• src/services/l402-config.ts (23.3% coverage)
• src/services/api-key.ts (23.52% coverage)

2. API Routes & Error Handling

• src/api/error-handler.ts (0% coverage)
• src/api/routes-readiness.ts (8.33% coverage)
• src/api/supervisor-auth.ts (14.28% coverage)
• src/api/routes.ts (25.05% coverage)

Recommendations

1. Error Handling & Readiness: Add unit tests for error-handler.ts and routes-readiness.ts to ensure API reliability during failures and deployments.
2. Services: The payment, licensing, and webhook subsystems currently have little to no test coverage. These are critical domain loops that need integration or unit tests.
3. API Key Management: api-key.ts coverage (23.52%) should be increased to ensure auth security measures behave correctly.

Action Items

• Write unit tests for src/services/licensing.ts and src/api/error-handler.ts.
• Add integration testing coverage for the webhooks and payment ledger operations.
• Add unit testing for API key service functions missing coverage.
• Aim to bring the overall statement coverage up to at least 60% as a short-term goal.

Note: This issue was automatically generated based on the recent test coverage review.

[dligthart]

Updated coverage review findings and shipped the first harness slice in 6431957 (test(harness): add coverage and ui test commands).

What landed:

• root test:coverage, test:ui, test:ui:coverage, and test:all scripts
• UI package test and test:coverage scripts
• shared Vitest setup to seed required test env vars so root tests do not crash purely because env secrets are unset

Review findings captured in this pass:

• coverage is still not an acceptable release gate because there are no enforced thresholds and full coverage runs remain brittle
• DB-backed suites still require reachable Postgres
• MCP HTTP tests still depend on real localhost socket binding
• critical supervisor routes like content/assets still need direct UI tests

Validated locally with:

• npm test -- --run src/api/auth.test.ts src/services/actor-identity.test.ts
• npm run test:coverage -- --run src/api/auth.test.ts

Next slice: stabilize DB/socket-dependent suites so the full coverage run can complete more reliably.

[dligthart]

Progress update since the original coverage review:

Implemented on main:

• coverage-oriented harness scripts: test:coverage, test:ui, test:ui:coverage, and test:all
• safer DB-backed test ergonomics: npm test now auto-applies committed repo migrations when the configured database is fresh or simply behind the Drizzle journal
• direct coverage additions for src/services/licensing.ts and src/api/error-handler.ts
• a full local npm test pass after the safe DB preflight work (62 files passed, 429 tests passed, 17 skipped)

Keeping this open for the remaining coverage work: broader payment/webhook/api-key/readiness coverage, stronger coverage gating, and any remaining full-suite reliability cleanup beyond the current DB bootstrap improvements.