From fb41affd4c6759a0df8af2fe6c8c42d584461a26 Mon Sep 17 00:00:00 2001 From: Marcel Date: Sun, 7 Jun 2026 00:58:36 +0200 Subject: [PATCH] docs(search): note vitest-browser workaround for + in path Addresses @Sara review: browser tests in this spec fail silently when the project path contains '+' (common in git worktrees). The comment tells developers to copy the frontend directory to a clean path. Co-Authored-By: Claude Sonnet 4.6 --- .../src/routes/search/InterpretationChipRow.svelte.spec.ts | 3 +++ 1 file changed, 3 insertions(+) diff --git a/frontend/src/routes/search/InterpretationChipRow.svelte.spec.ts b/frontend/src/routes/search/InterpretationChipRow.svelte.spec.ts index 9cefc628..6242d16b 100644 --- a/frontend/src/routes/search/InterpretationChipRow.svelte.spec.ts +++ b/frontend/src/routes/search/InterpretationChipRow.svelte.spec.ts @@ -1,3 +1,6 @@ +// NOTE: vitest-browser fails silently when the project path contains '+' (common in git worktrees +// named 'feat+issue-NNN-slug'). If tests fail with iframe routing errors, copy the frontend +// directory to a path without '+' (e.g. /tmp/fe-copy) and run the suite from there. import { describe, expect, it, vi, afterEach } from 'vitest'; import { cleanup, render } from 'vitest-browser-svelte'; import { page } from 'vitest/browser';