setup-browser-cookies

Import Chromium browser cookies into a headless session for QA testing.

4|1|Updated Sep 13, 2023
One-click install
npx skills add https://github.com/louisfghbvc/mcp-leetcode-crawler --skill setup-browser-cookies-louisfghbvc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: setup-browser-cookies
Source: https://github.com/louisfghbvc/mcp-leetcode-crawler/tree/main/.agent/skills/setup-browser-cookies
Command: npx skills add https://github.com/louisfghbvc/mcp-leetcode-crawler --skill setup-browser-cookies-louisfghbvc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Import cookies from your real Chromium browser into the headless browse session to authenticate QA testing workflows without manual login steps.

Core Features & Use Cases

  • Interactive cookie picker to choose which domains to import
  • Cookies persist in the headless session for multiple tests
  • Suitable for QA testing authenticated pages and pre-seeded sessions

Quick Start

Open the cookie picker, select domains to import, and confirm when finished.

Frequently Asked Questions about setup-browser-cookies

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I import cookies into a headless browser for QA testing?

To import cookies into a headless browser for QA testing, use an interactive picker to select cookie domains from your real Chromium browser and load them directly into the headless session for authenticated test workflows.

Can I use my real Chromium browser cookies for Playwright automated tests?

Yes, you can use your real Chromium browser cookies for Playwright automated tests by reading them from the browser and loading them into the headless session without requiring any code changes to your test scripts.

What is the best way to authenticate headless browser sessions without manual login?

The best way to authenticate headless browser sessions without manual login is to import cookies from your real Chromium browser into the headless session, bypassing manual login steps for QA testing workflows.

Do I need to modify my test code to load cookies into a headless session?

No, you do not need to modify your test code to load cookies into a headless session. Cookies are read from your real browser and loaded into the headless session automatically for subsequent automated tests.

How do I select which cookie domains to import for my automated tests?

You can select which cookie domains to import for your automated tests by using the interactive cookie picker, choosing the specific domains you need, and confirming your selection to load them into the headless session.

Do imported cookies persist across multiple tests in a headless browser session?

Yes, imported cookies persist in the headless browser session for multiple tests, allowing you to run QA testing on authenticated pages and pre-seeded sessions without needing to re-authenticate.