setup-browser-cookies

To import authenticated browser cookies into a headless testing environment, this skill securely transfers your local Chromium session cookies directly into the testing session, bypassing manual login flows for automated QA.

Automated QA tests often fail on protected web pages because headless environments lack active session cookies. Transferring authenticated cookies from your local browser provides the necessary login state to test these pages immediately.

The best way to bypass manual login for end-to-end testing is to inject existing authenticated session cookies from your local Chromium browser into the headless environment, eliminating login friction and starting tests immediately.

No, this cookie injection approach currently requires access to local Chromium browser cookie stores. It uses a specific binary to perform secure decryption and injection for QA testing environments.

To select specific domains for cookie import during automated testing, you can use the interactive visual picker provided by the skill, ensuring only the necessary credentials for your target site are transferred.

Yes, you need the gstack browse binary to perform secure decryption and injection of local browser cookies into the headless testing environment for your automated QA workflows.