Some checks failed
CI / Unit & Component Tests (push) Successful in 2m3s
CI / Backend Unit Tests (push) Successful in 2m5s
CI / E2E Tests (push) Has started running
CI / Unit & Component Tests (pull_request) Successful in 2m5s
CI / Backend Unit Tests (pull_request) Successful in 1m56s
CI / E2E Tests (pull_request) Failing after 18m40s
When the e2e profile is active, initE2EData (which creates a reader user) can run before initAdminUser. The old count() == 0 guard then skips admin creation entirely, causing every login test to fail with 401. Switch to findByUsername(adminUsername).isEmpty() so the admin is created regardless of which CommandLineRunner runs first. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>