setup-browser-cookies

To import real browser cookies into a headless Playwright session, use an interactive picker to select domains from your local Chromium-based browsers. The tool handles secure decryption and injects the authenticated cookies directly into the test context.

Yes, you can use your existing authenticated state for QA automation. The tool supports cookie import from Comet, Chrome, Arc, Brave, and Edge, allowing you to preserve login sessions across your automated testing environments.

You can target specific domains when injecting cookies into Playwright by using the interactive picker UI or via optional domain targeting flags in the CLI. This ensures only the required authenticated cookies are loaded into the test context.

The best way to test authenticated pages in headless testing without repeated logins is importing existing browser cookies. This bypasses authentication flows by directly loading decrypted cookies from your real browser profile into the Playwright context.

This cookie import approach currently works only with Chromium-based browsers. It explicitly supports cookie detection and decryption from Comet, Chrome, Arc, Brave, and Edge to inject into your Playwright session.

Playwright authenticated tests often fail headless because the session lacks valid cookies. Importing real browser cookies from your local profiles into the headless context preserves the authenticated state needed for QA automation.