skills.rest
TioSavich
TioSavichCOMMUNITY
Explore all skills by this author →
GitHub

setup-browser-cookies

Import cookies from real browsers into a headless Playwright session.

Updated Sep 10, 2024
Search Tags:#authentication#playwright#browser#headless#cookies#qa-testing
One-click install
npx skills add https://github.com/TioSavich/UMEDCTA --skill setup-browser-cookies-tiosavich
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: setup-browser-cookies
Source: https://github.com/TioSavich/UMEDCTA/tree/main/.claude/skills/gstack/setup-browser-cookies
Command: npx skills add https://github.com/TioSavich/UMEDCTA --skill setup-browser-cookies-tiosavich

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill makes it easy to bring cookies from your real browsers into a headless testing session, enabling authenticated QA without manual logins.

Core Features & Use Cases

  • Import cookies from Comet, Chrome, Arc, Brave, or Edge into a Playwright session.
  • Interactive picker to choose which cookie domains to import, saving time during QA testing of authenticated pages.
  • Use when you need to test with an already-logged-in state without performing a login flow.

Quick Start

Open the cookie picker, select the domains to import, and continue with your test.

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 real-browser cookies into a headless Playwright session?▼

You can import real-browser cookies into a headless Playwright session by using an interactive picker to select specific cookie domains. This enables authenticated QA testing without performing manual login flows.

Can I use cookies from Arc, Brave, or Edge for authenticated QA testing?▼

Yes, authenticated QA testing is supported with cookies imported from Arc, Brave, Edge, Chrome, and Comet. The tool provides an interactive picker to select which cookie domains to load into your session.

What is the best way to test authenticated pages in Playwright without logging in?▼

The best way to test authenticated pages without logging in is to load existing cookies from a real browser into your headless session. This skips the login flow by transferring an already-logged-in state directly.

Do I need to manually select cookie domains when importing browser cookies for testing?▼

You need to use an interactive picker to select which cookie domains to import, saving time during QA testing. This ensures only the necessary authenticated states are loaded into the headless Playwright session.

Does importing cookies into Playwright include verification steps?▼

Yes, importing cookies into Playwright includes both setup and verification steps. This ensures the authenticated session is properly established and validated before you continue with your headless testing.

Related Skills

Explore More Software Engineering Skills→
shihwesleyshihwesley

setup-browser-cookies

Import cookies from installed browsers into Playwright sessions for authenticated QA testing.

Community
Intermediate
wormholecowboywormholecowboy
1

agent-browser

Automate browser tasks via CLI with headless Chromium.

Community
Intermediate
YangYuS8YangYuS8

playwright-cli

Automate browser testing workflows with Playwright via a CLI.

Community
Intermediate
ollieb89ollieb89

auth-implementation-patterns

Implement JWT, OAuth2, and RBAC authentication across APIs and web apps.

Community
Advanced