docs: strengthen dynamic engine test evidence

2026-07-19 02:01:33 +08:00
parent 42df227feb
commit f90a3bd1cb
1 changed files with 3 additions and 0 deletions
@@ -519,6 +519,7 @@ git commit -m "feat: score dynamic birth time choices"
 - Test: `frontend/tests/birth-time-journey-engine.test.ts`
 - Test: `frontend/tests/birth-time-journey-adapters.test.ts`
 - Test: `frontend/tests/birth-time-journey-dynamic-adapters.test.ts`
+- Test support: `frontend/tests/birth-time-journey-memory-store.ts`

 **Interfaces:**
 - Adds `buildDifferencePacket(input: DifferencePacketInput): Promise<CandidateDifferenceBuild>`.
@@ -602,6 +603,8 @@ Place all v2 response schemas and mappings in `birth-time-journey-dynamic-adapte

 Test authentication through an executable fake fetch/wire seam for both dynamic endpoints: exact URL, bearer header, request body, timeout signal, and missing-token fail-before-fetch. Also prove legacy calls omit the dynamic Authorization header. The HTTP helper accepts one typed request/options object rather than four primitive parameters.

+Wire assertions use independent literal request expectations, not the production serializer as the expected value. Inject the timeout-signal factory in tests and assert it receives the literal `45_000`; do not infer the timeout from a sibling exported constant. If a pre-existing test-support module exceeds the limit, extract the memory journey store into `birth-time-journey-memory-store.ts` instead of compressing formatting to pass the LOC check.
+
 - [ ] **Step 5: Verify endpoint payload ownership**

 Add a source-level test asserting that `candidate_scores` appears only in server modules and never in `birth-time-journey-client.ts`, `birth-time-journey-request.ts`, or a component/hook.