Add a 4-layer test stack covering RLS, triggers, and UI flows for Fases 0–2a, then restructure every plan file so future fases start with tests and end with a verification gate. Test suite - packages/test-utils: Vitest integration tests signing HS256 JWTs via jose so each test acts as a specific seed user (createClientAs + createAdminClient) - supabase/tests: pgTAP for accept_invitation(), item_frequency trigger, and promote-on-admin-leave; each file self-installs pgtap extension - apps/web/tests: Playwright E2E with live Keycloak login per test (storageState caching doesn't rehydrate Supabase's session state reliably) - just test-all chains the three suites; test-db forwards POSTGRES_PASSWORD as PGPASSWORD with ON_ERROR_STOP=1 so failures abort the chain Supabase auth gotcha - PostgREST queries inside onAuthStateChange deadlock on GoTrue's navigator.locks auth lock (getAccessToken → getSession → initializePromise waits on the same lock that's held during event dispatch). Fix is two defenses: a pass-through lock in $lib/supabase, and a setTimeout(0) defer in root +layout.svelte to push loadUserCollectives out of the callback's microtask chain. Either alone is insufficient; both together unblock the Playwright suite. Env key rotation - apps/web/.env.development had a stale demo anon key signed with a different secret than root .env; Vite inlined that into the browser bundle so Kong (which uses the root .env value) rejected every request with 401. Aligned the two files and added a memory entry to flag this for the next rotation. Plan restructure (TDD) - Every fase now opens with X.0 Tests primero and closes with X.Z Verificación final. Completed fases (0, 1, 2a) show the pattern retroactively with the tests that currently cover them; pending fases (2b, 3, 4) list the tests to write before implementation. Docs - CLAUDE.md status line reports 54 + 12 + 15 = 81 green tests, adds gotchas #11 (auth-lock deadlock) and #12 (no storageState caching) - README.md adds a TDD methodology section and the test-all command - .gitignore excludes Playwright's generated reports and auth state 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
83 lines
2.9 KiB
PL/PgSQL
83 lines
2.9 KiB
PL/PgSQL
-- pgTAP: fn_record_item_frequency trigger — D/E-series
|
|
-- Verifies the SECURITY DEFINER trigger populates item_frequency correctly.
|
|
-- Run with: psql -U postgres -d postgres -f supabase/tests/002_item_frequency_trigger.sql
|
|
|
|
CREATE EXTENSION IF NOT EXISTS pgtap;
|
|
|
|
-- Note: tests E-02/E-03/E-04 (RLS rejection of direct writes) are covered by
|
|
-- the Vitest integration suite (packages/test-utils/tests/rls-frequency.test.ts)
|
|
-- which connects as an authenticated role. The postgres superuser bypasses RLS
|
|
-- entirely, so pgTAP cannot assert those policies here.
|
|
|
|
BEGIN;
|
|
SELECT plan(3);
|
|
|
|
-- Setup: temporary list for item insertion
|
|
INSERT INTO public.shopping_lists (id, collective_id, name, status, created_by)
|
|
VALUES (
|
|
'cccccccc-cccc-cccc-cccc-cccccccccccc',
|
|
'aaaaaaaa-aaaa-aaaa-aaaa-aaaaaaaaaaaa',
|
|
'Trigger test list',
|
|
'active',
|
|
'11111111-1111-1111-1111-111111111111'
|
|
) ON CONFLICT (id) DO NOTHING;
|
|
|
|
-- D-13: Inserting an item creates a new frequency row (normalized name)
|
|
INSERT INTO public.shopping_items (list_id, name, quantity, unit, sort_order, created_by)
|
|
VALUES ('cccccccc-cccc-cccc-cccc-cccccccccccc', ' Butter ', 1, NULL, 50, '11111111-1111-1111-1111-111111111111');
|
|
|
|
SELECT ok(
|
|
EXISTS (
|
|
SELECT 1 FROM public.item_frequency
|
|
WHERE collective_id = 'aaaaaaaa-aaaa-aaaa-aaaa-aaaaaaaaaaaa'
|
|
AND name = 'butter'
|
|
),
|
|
'D-13: trigger normalises name (lower+trim) and inserts into item_frequency'
|
|
);
|
|
|
|
-- D-14: Inserting the same item again increments use_count
|
|
DO $$
|
|
DECLARE v_count_before integer;
|
|
BEGIN
|
|
SELECT use_count INTO v_count_before
|
|
FROM public.item_frequency
|
|
WHERE collective_id = 'aaaaaaaa-aaaa-aaaa-aaaa-aaaaaaaaaaaa'
|
|
AND name = 'butter';
|
|
|
|
INSERT INTO public.shopping_items (list_id, name, sort_order, created_by)
|
|
VALUES ('cccccccc-cccc-cccc-cccc-cccccccccccc', 'Butter', 51, '11111111-1111-1111-1111-111111111111');
|
|
END $$;
|
|
|
|
SELECT ok(
|
|
(SELECT use_count FROM public.item_frequency
|
|
WHERE collective_id = 'aaaaaaaa-aaaa-aaaa-aaaa-aaaaaaaaaaaa'
|
|
AND name = 'butter') >= 2,
|
|
'D-14: use_count increments on repeated INSERT'
|
|
);
|
|
|
|
-- D-15: Trigger does not fire on UPDATE (only on INSERT)
|
|
-- (PostgreSQL does not allow LIMIT on UPDATE — use a ctid subquery instead.)
|
|
DO $$
|
|
BEGIN
|
|
UPDATE public.shopping_items
|
|
SET name = 'Butter'
|
|
WHERE ctid = (
|
|
SELECT ctid FROM public.shopping_items
|
|
WHERE list_id = 'cccccccc-cccc-cccc-cccc-cccccccccccc'
|
|
AND name = 'Butter'
|
|
LIMIT 1
|
|
);
|
|
END $$;
|
|
|
|
-- We can't easily compare before/after in a single statement in pgTAP without
|
|
-- a custom helper. Instead just verify the count is still reasonable (> 0).
|
|
SELECT ok(
|
|
(SELECT use_count FROM public.item_frequency
|
|
WHERE collective_id = 'aaaaaaaa-aaaa-aaaa-aaaa-aaaaaaaaaaaa'
|
|
AND name = 'butter') > 0,
|
|
'D-15: item_frequency still intact after item UPDATE'
|
|
);
|
|
|
|
SELECT * FROM finish();
|
|
ROLLBACK;
|