From 0c48ea9080e7db57ae154a1f874f02c83ccb962b Mon Sep 17 00:00:00 2001 From: Andy Stark Date: Mon, 12 Oct 2026 10:33:49 +0100 Subject: [PATCH 1/2] DOC-7171 Update TCE testing notes: Lettuce pins and captured stdout Promotes two lessons from the HOTKEYS examples (PR #4241). The Java divergence table said portable Lettuce was 6.5.5, but only pom-lettuce-sync.xml is; async and reactive are 7.7.0, so lettuce-sync can't compile 7.x APIs in portable mode. Also notes that cargo test and xunit capture stdout, so REMOVE asserts are the only check on Rust and C# >>> comments. Ticket: DOC-7171 Co-Authored-By: Claude Opus 5.5 --- .claude/skills/tce-examples/reference/testing.md | 15 +++++++++++---- 1 file changed, 11 insertions(+), 4 deletions(-) diff --git a/.claude/skills/tce-examples/reference/testing.md b/.claude/skills/tce-examples/reference/testing.md index ca50f95899..d7c0ce557e 100644 --- a/.claude/skills/tce-examples/reference/testing.md +++ b/.claude/skills/tce-examples/reference/testing.md @@ -106,12 +106,19 @@ These are all real failures that produced green results before: reported as four passing clients — and an NRedisStack-flavoured file gets credited to the SE.Redis tab. +One trap it does **not** guard against: `cargo test` (Rust) and xunit (C#) capture stdout, +so their logs can't be compared with the `>>>` comments. For those clients, make the REMOVE +asserts cover every printed value — they are the only check the comments get. + ## Known divergence: Java versions -| | jedis | lettuce-core | -|---|---|---| -| portable (`pom-*.xml`) | 7.5.3 | 6.5.5.RELEASE | -| fidelity (`fidelity/pom-*.xml`) | 7.4.0 | 7.4.0.RELEASE | +| | jedis | lettuce-sync | lettuce-async / reactive | +|---|---|---|---| +| portable (`pom-*.xml`) | 7.5.3 | 6.5.5.RELEASE | 7.7.0.RELEASE | +| fidelity (`fidelity/pom-*.xml`) | 7.4.0 | 7.4.0.RELEASE | 7.4.0.RELEASE | + +Portable lettuce-sync lags the other two: an example using any API newer than 6.5 (for +example HOTKEYS, added in 7.4) fails to compile there, so test lettuce-sync with `--fidelity`. Not yet reconciled. The fidelity pins are what the current `local_examples/` Java files were actually tested against, so they're the known-good pair; the portable jedis 7.5.3 bump was From eb9b3c00976218c0a4ca01b67131e8867fc05c4b Mon Sep 17 00:00:00 2001 From: Andy Stark Date: Tue, 13 Oct 2026 15:26:20 +0100 Subject: [PATCH 2/2] DOC-7171 Drop Lettuce-Sync --fidelity advice superseded by DOC-7172's Known gap section Co-Authored-By: Claude Opus 5.5 --- .claude/skills/tce-examples/reference/testing.md | 3 --- 1 file changed, 3 deletions(-) diff --git a/.claude/skills/tce-examples/reference/testing.md b/.claude/skills/tce-examples/reference/testing.md index d7c0ce557e..627a2b91b2 100644 --- a/.claude/skills/tce-examples/reference/testing.md +++ b/.claude/skills/tce-examples/reference/testing.md @@ -117,9 +117,6 @@ asserts cover every printed value — they are the only check the comments get. | portable (`pom-*.xml`) | 7.5.3 | 6.5.5.RELEASE | 7.7.0.RELEASE | | fidelity (`fidelity/pom-*.xml`) | 7.4.0 | 7.4.0.RELEASE | 7.4.0.RELEASE | -Portable lettuce-sync lags the other two: an example using any API newer than 6.5 (for -example HOTKEYS, added in 7.4) fails to compile there, so test lettuce-sync with `--fidelity`. - Not yet reconciled. The fidelity pins are what the current `local_examples/` Java files were actually tested against, so they're the known-good pair; the portable jedis 7.5.3 bump was deliberate (the search examples need the `RedisClient` API it introduced). Settling on one