setup-browser-cookies

To import real browser cookies into a headless Playwright session for QA testing, you use an interactive picker to select specific cookie domains, which are then decrypted and loaded into the headless browser context to preserve authenticated states.

Yes, you can use Chromium browser cookies for authenticated testing in a headless environment by decrypting and injecting them into the Playwright session, allowing QA tests to bypass login flows on authenticated pages.

You can select which cookie domains to load into your headless QA browser using an interactive cookie picker UI, ensuring only the relevant authenticated contexts are imported into the Playwright session.

Yes, a Bash-based runtime is required to execute the decryption and injection process that loads real Chromium browser cookies into the Playwright headless session for QA testing.

Headless browsers fail to test authenticated pages without importing cookies because they start with empty sessions, requiring decrypted real browser cookies to be injected to preserve the necessary authenticated context.