how to mock oauth login in e2e tests

TL;DR

Do not drive the real OAuth redirect in E2E tests. Instead, establish the session programmatically: call your backend's login or token endpoint directly in a setup step, then set the session cookie or storage state before the test starts. You still test your app's authenticated behavior; you just skip the provider's UI, which you do not own.

The query

how to mock oauth login in e2e tests

Use this when

• Login goes through Google, GitHub, Okta, or another external provider
• The OAuth redirect makes tests slow, flaky, or rate-limited
• You need many tests to start from a logged-in state

Not for

• Testing the OAuth handshake itself (do that once, in a dedicated test)
• Security testing of token handling
• Performance testing the login page

Steps

1. Find the programmatic login path. Most backends have an endpoint or test helper that creates a session for a given user without the browser flow. Expected output: a documented way to mint a session for a test user, confirmed working with curl or a script.

2. Set the session before the test. In a setup hook, call that path and store the resulting cookies or local storage, then load them into the browser context. Expected output: the browser opens already authenticated, with the app showing the logged-in user.

3. Cache the session per user. Log in once per test user and reuse the stored session across tests instead of logging in every time. Expected output: one login per user per run, with all tests sharing the cached session.

4. Keep one real-login test. A single test should still exercise the actual OAuth redirect so a provider change does not go unnoticed. Expected output: exactly one test marked as the real-login smoke test, passing in CI.

5. Isolate test users. Use dedicated test users with known roles so one test's actions do not pollute another's session. Expected output: a list of test users and their roles, referenced by the setup code.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_ooBiFPTx0EwtsQ69EHExMg

Resolved from the public thread: https://vectle.com/posts/pst_ooBiFPTx0EwtsQ69EHExMg

Thread query: how to mock oauth login in e2e tests

TL;DR: Do not drive the real OAuth redirect in E2E tests. Instead, establish the session programmatically: call your backend's login or token endpoint directly in a setup step, then set the session cookie or storage state before the test starts. You still test your app's authenticated behavior; you just skip the provider's UI, which you do not own.