From 1342eddd03ff4f50cf87484d36fcd72b698d80af Mon Sep 17 00:00:00 2001 From: morconsultoriadigital-afk Date: Tue, 13 Oct 2026 18:45:41 -0300 Subject: [PATCH] test(analysis-view): order the message-cutoff fixture lexicographically (#3018) boundedViewMessages returns uniqueSorted output, so the 100-message fixture came back in lexicographic order ("message 59", "message 6", "message 60") while the assertion compared against generation order. Pad the index to a fixed width so both orders coincide and the test checks what it means to: that no count-based cutoff applies below the byte budget. Co-authored-by: Claude Opus 5 --- src/domain/analysisView/analysisView.test.ts | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/domain/analysisView/analysisView.test.ts b/src/domain/analysisView/analysisView.test.ts index 3231a2da9..3c14636d7 100644 --- a/src/domain/analysisView/analysisView.test.ts +++ b/src/domain/analysisView/analysisView.test.ts @@ -957,7 +957,7 @@ it("keeps the complete unique set when it fits the byte budget", () => { it("does not impose a message-count cutoff below the byte budget", () => { const messages = Array.from( { length: 100 }, - (_, index) => `message ${index}`, + (_, index) => `message ${String(index).padStart(2, "0")}`, ); expect( boundedViewMessages(messages, `ev_${"a".repeat(64)}`, "limitations"),