Playwright Auth (Clerk)

Authenticating Playwright tests with Clerk without passwords or MFA is done by programmatically generating Clerk sign-in tokens. This bypasses CAPTCHA and password prompts, allowing you to retrieve tokens from the Clerk API and establish a seamless login session for end-to-end testing.

To set up Clerk authentication for Playwright testing, you need a CLERK_SECRET_KEY, an existing Clerk user account, and an application that loads Clerk JS on the frontend. These prerequisites allow the test runner to retrieve tokens and wait for session readiness.

Yes, you can reuse authenticated Clerk state across multiple Playwright test cases. The process generates a Clerk sign-in token, waits for Clerk JS readiness, and saves the authenticated state, enabling you to restore the session for subsequent tests without repeating the login flow.

Auth races in CI with Convex JWT occur when tests proceed before the authentication cache is fully populated. You can reduce these races by optionally warming the Convex JWT cache after generating the Clerk sign-in token, ensuring the authenticated state is fully ready before tests execute.

The best way to automate Clerk sign-in for test automation is to use the Clerk API to programmatically generate sign-in tokens. This approach eliminates flaky logins and password downtime by bypassing manual authentication steps like MFA and CAPTCHA.

No, this approach requires the application to load Clerk JS on the frontend. The authentication process depends on waiting for Clerk JS readiness to restore the authenticated state and successfully apply the generated sign-in tokens in the browser environment.