Till JS 09f81d77de test(integration): assert security_events audit rows after register + login ... Adds two assertions to the auth-flow integration test that exercise the audit-log path: - after register: expect exactly 1 REGISTER row in auth.security_events for the new user - after login: expect exactly 1 LOGIN_SUCCESS row for the same user This locks in the fix from the previous commit (security.ts ?? null guard for optional fields) and catches any future regression where security.logEvent silently swallows a SQL error and the audit log goes into the void. Verified by reverting security.ts to the broken pre-fix version and re-running — the test fails with `Expected: 1, Received: 0` at the register-audit assert in 211ms instead of taking hours of production debugging. Also adds an explicit DELETE FROM auth.security_events to the afterAll cleanup. The FK from security_events.user_id to auth.users(id) is ON DELETE CASCADE so it would clean up implicitly anyway, but listing it explicitly makes the cleanup intent obvious from the test source. Net: 24 → 26 expects per run. Still ~22s end-to-end on a warm cache.		2026-04-08 18:05:57 +02:00
..
e2e	first implementation	2025-11-27 17:26:18 +01:00
integration	test(integration): assert security_events audit rows after register + login	2026-04-08 18:05:57 +02:00