From f41711a6ed3da17f63b4171566e14cd3dbffc774 Mon Sep 17 00:00:00 2001 From: Lucas Winther Date: Fri, 18 Sep 2026 11:44:01 +0200 Subject: [PATCH] docs: fix unsatisfiable exact-mode test in plan Task 9 The test used query 'certificat', which is a literal substring of the fixture's 'certificate' comment text. Exact mode is substring containment by design, so the query matched and the toHaveLength(0) assertion could never pass. Replaced with an insertion typo, which cannot be a substring of the shorter original. Co-Authored-By: Claude Opus 5 (1M context) --- docs/plans/2026-09-17-fuzzy-search-plan.md | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/docs/plans/2026-09-17-fuzzy-search-plan.md b/docs/plans/2026-09-17-fuzzy-search-plan.md index e3c926d..d079342 100644 --- a/docs/plans/2026-09-17-fuzzy-search-plan.md +++ b/docs/plans/2026-09-17-fuzzy-search-plan.md @@ -2878,8 +2878,12 @@ describe("Activity Ranking", () => { }); test("exact mode finds nothing for a typo", async () => { + // "certificatee" is an INSERTION typo: by construction it cannot be a + // substring of the shorter "certificate" in the fixture. A truncation + // typo like "certificat" would not work here — exact mode is substring + // containment, so a truncation still matches and the test could never pass. const result = await listWorkPackageActivities( - { workPackageId: 1, query: "certificat", matchMode: "exact" }, + { workPackageId: 1, query: "certificatee", matchMode: "exact" }, activitiesClient() ); expect(result).toHaveLength(0);