From 1506ab76ed082553072095f576400afac77eb17f Mon Sep 17 00:00:00 2001 From: Claude Date: Mon, 17 Aug 2026 14:52:35 +0000 Subject: [PATCH] docs(spec): correct finder test coverage claim The review stated the finder had no e2e coverage and that 209-rundown-shortcuts.spec.ts never opened it. Both are wrong: a "Find in rundown" smoke test opens the modal and closes it with Escape. Describe the coverage that exists and what it leaves unguarded. Co-Authored-By: Claude Opus 5 Claude-Session: https://claude.ai/code/session_01DzALEq9gGWwFmwTdgAiFcY --- apps/spec/finder.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/apps/spec/finder.md b/apps/spec/finder.md index 81d123bb7..9a0d26a35 100644 --- a/apps/spec/finder.md +++ b/apps/spec/finder.md @@ -79,8 +79,10 @@ refetch). Build from raw `rundown.entries` + `flatOrder`, memoised on **`rundown ### 1.6 Tests -None — no unit, no component, no e2e. `useSelectAndRevealEntry` is untested too. -`e2e/tests/features/209-rundown-shortcuts.spec.ts` never opens the Finder. +No unit or component tests, and `useSelectAndRevealEntry` is untested too. E2E coverage is a single +smoke test — `Find in rundown` in `e2e/tests/features/209-rundown-shortcuts.spec.ts` opens the modal +with `mod+F` and closes it with `Escape`. Nothing exercises searching, selecting, or navigating +results, so every behaviour described above is unguarded. ---