clusters-swipes specs fail on origin/dev: Settings view has 5 stops, specs need 8 #474

Open
opened 2026-11-09 12:27:05 +00:00 by kayg · 0 comments
Owner

apps/tracer/test/clusters-swipes.spec.ts (2 tests) and clusters-swipes-both.spec.ts (the 2 horizontal tests) fail on plain origin/dev 80a09ad02, before any wheel-router change. Found while working on #444.

Evidence (dev-02, production build; identical on origin/dev and on branch swipe-content-first-d374, logs j408-base.spec.log and j408-head.spec.log):

  • clusters-swipes: expect(lock.stops).toBeGreaterThanOrEqual(8), received 5. The Settings view now frames five stops, so six swipes can never land six windows further.
  • clusters-swipes-both: six horizontal swipes move 3 windows, not 6 (same cause: five stops).

I tried the Docs view as a replacement fixture (it has 12 windows). In the mock scene scene=1&docs=1 the Docs view is a free view: canvasLock().on is false and no framed pill exists, so the spec failed differently. A proper fix needs a snapped view with at least seven stops, for example a scene built for the purpose. Not a wheel-routing conflict: the specs dispatch on the viewport or a window, and the router gives those to the canvas. Needs its own owner.

`apps/tracer/test/clusters-swipes.spec.ts` (2 tests) and `clusters-swipes-both.spec.ts` (the 2 horizontal tests) fail on plain origin/dev 80a09ad02, before any wheel-router change. Found while working on #444. Evidence (dev-02, production build; identical on origin/dev and on branch `swipe-content-first-d374`, logs `j408-base.spec.log` and `j408-head.spec.log`): - clusters-swipes: `expect(lock.stops).toBeGreaterThanOrEqual(8)`, received 5. The Settings view now frames five stops, so six swipes can never land six windows further. - clusters-swipes-both: six horizontal swipes move 3 windows, not 6 (same cause: five stops). I tried the Docs view as a replacement fixture (it has 12 windows). In the mock scene `scene=1&docs=1` the Docs view is a free view: `canvasLock().on` is false and no framed pill exists, so the spec failed differently. A proper fix needs a snapped view with at least seven stops, for example a scene built for the purpose. Not a wheel-routing conflict: the specs dispatch on the viewport or a window, and the router gives those to the canvas. Needs its own owner.
Sign in to join this conversation.
No labels
launch-qa
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
kayg/infraternal#474
No description provided.