setup-browser-cookies

You can import real browser cookies into a headless Playwright session by using a tool that decrypts and loads authenticated session cookies from installed Chromium browsers. This process requires interactive domain selection to specify which cookie sessions to sync for your QA tests.

Headless browser sessions start fresh without cookies, meaning they lack the login state of your installed browsers. To resolve this, you need to import authenticated session cookies from your local Chromium browser into the headless session before executing QA tests.

The best way to test authenticated pages without manual login is importing existing browser cookies into the headless session. This approach decrypts your local Chromium cookie store and applies it to Playwright, bypassing repetitive logins and reducing test flakiness.

Yes, you can select specific cookie domains to import into your Playwright test session. The cookie import process features an interactive domain picker UI, giving you precise control over which authenticated sessions are synced to the headless browser.

Yes, you need the gstack browse binary to decrypt Chromium cookies for headless testing. This binary handles the decryption and loading of the browser cookie stores, enabling the transfer of authenticated sessions into the Playwright environment.

Limitations of using imported browser cookies include dependency on the gstack browse binary and local Chromium browser installations. Additionally, imported sessions may expire or invalidate if the original browser logs out, potentially causing headless QA tests to fail unexpectedly.