setup-browser-cookies

To import browser cookies into a headless Chromium session for QA automation, you select your specific domain interactively, load the decrypted cookies, and verify the imported cookie count to establish an authenticated state. This enables testing authenticated pages without retyping credentials.

You need to import browser cookies for authenticated testing in Playwright to access real login states in headless sessions. This solves the problem of fighting manual cookie setup or retyping credentials, allowing you to directly test authenticated pages during QA runs or bug repros.

To select specific domains when transferring browser cookies for session import, you use the interactive browser detection and import picker. This domain-level cookie selection ensures you only move the login state for the sites you need into your headless Chromium environment.

Yes, the cookie import process includes a verification step that shows the imported cookie counts after the transfer. This ensures your decrypted browser cookies were successfully loaded into the headless session before you begin your QA testing or authenticated page checks.

Yes, you can use your existing login state for authenticated page checks without retyping credentials. By importing your real Chromium browser cookies into the headless session, you replicate the authenticated environment instantly for workflows like bug repros and QA runs.