auth-supabase-otp

Supabase passwordless OTP testing is automated by driving the login flow with Playwright, retrieving the OTP directly from the database via a service role, and verifying access to protected pages. This orchestrates login, OTP retrieval, and verification end-to-end.

Automated OTP retrieval works by using the Supabase service role for database access to fetch the generated code after the login flow is triggered. This bypasses email delivery, allowing tests to directly query and input the code for verification.

Yes, you can use both fixed and dynamic test users for Supabase OTP authentication tests. The skill loads configuration from project.json, allowing you to define test user modes alongside the authentication method and provider for flexible QA and CI environments.

The best way to test Supabase passwordless login flows in CI is using config-driven end-to-end orchestration that navigates the login page, fetches the OTP from the database, and verifies authenticated access, ensuring reusable validation across integration environments.

Yes, you need a Supabase service role key to test OTP authentication end-to-end. The service role is required for direct database access to retrieve the OTP, bypassing the need for email interception during your automated Playwright test runs.