Files
collective-lists/packages/test-utils/tests/sync-queue.test.ts
Oier Bravo Urtasun cb07f67a69 feat(realtime): full Fase 2b.0 test suite + infra hardening
Extend the 2b.0 red-phase coverage: presence, RLS isolation, offline-queue
contract, and Playwright scaffolds for the shopping-session UX. Only the
presence test is blocked on an upstream Realtime bug (documented below); all
other Realtime paths are proven end-to-end.

Tests
- realtime-postgres-changes.test.ts: now uses afterEach socket disconnect
  (Vitest singleFork kept Phoenix sockets alive between files, leaking state)
- realtime-isolation.test.ts (new): R-I-01 David (guest, same collective)
  receives events; R-I-02 Eva (non-member) receives NONE — RLS is enforced
  server-side per subscribed JWT
- realtime-presence.test.ts (new, describe.skip): two-client roster + leave
  assertions ready, gated on upstream bug
- sync-queue.test.ts (new, describe.skip): 7 placeholders pinning the
  apps/web/src/lib/sync/queue.ts contract (Q-01..Q-04 enqueue / in-order
  flush / retry; F-01..F-03 online-event flush + last-write-wins)
- apps/web/tests/e2e/{session,realtime,offline}.test.ts (new, describe.skip):
  S-01..S-03, R-E-01, R-E-02, O-01, O-02 pinning the Modo Compra UI contract
- vitest.config.ts: fileParallelism=false, drop singleFork so each file gets
  a fresh worker fork — prevents RealtimeClient singleton leakage

Infra
- db-init/00-role-passwords.sh: pre-create `realtime` schema with
  AUTHORIZATION supabase_admin. Realtime's per-tenant migrator creates tables
  INSIDE the schema but does not create the schema itself; without this the
  first tenant connect fails with "schema realtime does not exist"
- docker-compose.dev.yml: adopt the upstream supabase/supabase Realtime env
  shape — SEED_SELF_HOST=true + RUN_JANITOR=true + RLIMIT_NOFILE=10000 +
  drop the custom `command: eval seeds` (that bypasses the normal supervisor
  startup and was observed to cause GenServer crashes under load).
  Version pinned to v2.76.5 to match the official docker-compose.

Known upstream bug
- Realtime v2.76.5 and v2.83.0 both crash on presence_diff:
  `(UndefinedFunctionError) RealtimeChannel.handle_out/3 is undefined`.
  postgres_changes + isolation unaffected (they don't traverse handle_out).
  Presence tests stay `describe.skip` until a fixed upstream is released.

Totals: 59 Vitest passed (+ 9 skipped awaiting implementation/upstream),
16 pgTAP, 15 Playwright (+ 7 E2E scaffolded for 2b UI) = 90 green.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
2026-04-13 02:55:55 +02:00

70 lines
2.8 KiB
TypeScript

/**
* Sync queue unit tests (Fase 2b.2).
*
* These describe the contract of the offline mutation queue that will live at
* `apps/web/src/lib/sync/queue.ts`. They are skipped until that module exists.
* When implementation lands, remove the `describe.skip` (NOT the inner skips)
* and each test should fail red → pass green as features are built.
*
* Why they're here (not in apps/web): keeping all Vitest tests in one package
* for `just test-integration`. If we ever add Vitest to apps/web directly, move
* these files over and drop the cross-package import.
*/
import { describe, it, expect } from 'vitest';
describe.skip('sync queue — pending_ops contract (Fase 2b.2)', () => {
it('Q-01: enqueue writes the op to pending_ops before the Supabase call', async () => {
// Given a mocked idb + mocked supabase.from().insert()
// When sync.enqueue({ op: "insert", table: "shopping_items", payload })
// Then pending_ops should contain the op before the supabase call fires,
// and the supabase call should only be awaited after the write.
expect(true).toBe(true); // placeholder
});
it('Q-02: successful sync removes the op from pending_ops', async () => {
// Given an op in pending_ops
// When the supabase call resolves with no error
// Then the op should be removed from pending_ops
expect(true).toBe(true);
});
it('Q-03: failed sync keeps the op in pending_ops for retry', async () => {
// Given an op in pending_ops
// When the supabase call throws (network error)
// Then the op remains, its `attempts` counter increments,
// and the promise resolves (does NOT throw) — errors are deferred
// so callers can keep working offline.
expect(true).toBe(true);
});
it('Q-04: ops are processed in insertion order on flush', async () => {
// Given three ops A, B, C in pending_ops in that order
// When flush() runs
// Then supabase calls happen in A, B, C order regardless of timing
expect(true).toBe(true);
});
});
describe.skip('sync flush — online event fallback (Fase 2b.2, Safari-safe)', () => {
it('F-01: window "online" event triggers flush()', async () => {
// Given pending ops and a mocked window
// When dispatch Event("online")
// Then flush() is called within 100ms
expect(true).toBe(true);
});
it('F-02: last-write-wins on conflict — remote updated_at > local', async () => {
// Given a local op that would overwrite a remote row with a newer updated_at
// When flush runs
// Then the local op is DROPPED (not retried) and a sync_conflicts row is written
expect(true).toBe(true);
});
it('F-03: last-write-wins — local updated_at > remote, local wins', async () => {
// Given a local op newer than the remote row
// When flush runs
// Then the local op is APPLIED normally, no conflict row
expect(true).toBe(true);
});
});