refactor: extract API route test harness #366

New issue

Closed

opened 2026-05-11 21:02:07 +00:00 by barrettruth · 0 comments

barrettruth commented

2026-05-11 21:02:07 +00:00

Owner

Parent: #355

Problem

API route tests repeat hoisted DB/user state, DB mocks, auth middleware mocks, encryption-key setup, and JSON helper boilerplate. This makes new route tests noisy and easy to wire incorrectly.

Solution

Create a small API route test harness:

centralize common DB/auth/encryption setup where Vitest hoisting allows it
centralize request/response JSON helpers
migrate a small representative set first, then expand if safe

Acceptance criteria

At least three existing API route test files use the harness.
Hoisting order remains reliable.
Full API test suite passes.

Parent: #355 ## Problem API route tests repeat hoisted DB/user state, DB mocks, auth middleware mocks, encryption-key setup, and JSON helper boilerplate. This makes new route tests noisy and easy to wire incorrectly. ## Solution Create a small API route test harness: - centralize common DB/auth/encryption setup where Vitest hoisting allows it - centralize request/response JSON helpers - migrate a small representative set first, then expand if safe ## Acceptance criteria - At least three existing API route test files use the harness. - Hoisting order remains reliable. - Full API test suite passes.

barrettruth added the

track:api

type:cleanup

labels

2026-05-11 21:02:07 +00:00

barrettruth referenced this issue

2026-05-11 21:02:45 +00:00

tracker: foundation hardening before Google sync #355

barrettruth referenced this issue from a pull request that will close it,

2026-05-11 21:35:01 +00:00

refactor: extract API route test harness #381

barrettruth closed this issue