setup-browser-testing

Initialize or repair Playwright or Cypress browser-test infrastructure for Node projects.

1|Updated Apr 15, 2026
One-click install
npx skills add https://github.com/pnewsam/skills --skill setup-browser-testing-pnewsam
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: setup-browser-testing
Source: https://github.com/pnewsam/skills/tree/main/archive/setup-browser-testing
Command: npx skills add https://github.com/pnewsam/skills --skill setup-browser-testing-pnewsam

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Setting up browser testing from scratch involves many fragile decisions: choosing a framework, matching the package manager, wiring the dev server, handling authentication, and configuring CI. This Skill establishes or repairs a complete, documented browser-test foundation without breaking existing setup or committing unwanted changes. ## Core Features & Use Cases - Framework setup and repair: Preserves an existing Playwright or Cypress configuration, or installs Playwright when none exists, using the repository's own package manager and lockfile. - Smoke test and auth boundary: Adds one deterministic smoke test against a verified route, and builds authentication fixtures only when the real login contract is known. - CI and documentation: Adds a minimal CI job aligned with existing workflows and writes a test README documenting commands, structure, and environment variables. - Use Case: A monorepo package has no end-to-end tests. The Skill detects pnpm, installs Playwright, configures the dev server on the correct port, adds a smoke test and a pull-request CI job, and documents everything. ## Quick Start Use the setup-browser-testing skill to establish a working Playwright test foundation for this project.

Frequently Asked Questions about setup-browser-testing

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

FAQPage Schema
How do I set up Playwright testing in an existing Node project?▼

Install @playwright/test as a dev dependency with your existing package manager, create a playwright.config.ts pointing at your verified dev-server command and base URL, and add one deterministic smoke test. This Skill automates that flow while preserving existing configuration.

Playwright vs Cypress for end-to-end testing setup?▼

The Skill preserves whichever framework already exists in the repository. When neither is present, it defaults to Playwright unless repository instructions or the user specify Cypress, and it never replaces a working setup with a generic template.

Does it work in a monorepo with multiple packages?▼

Yes. It reads workspace configuration such as pnpm-workspace.yaml to identify the package that owns the browser experience, then scopes installation and configuration to that package. If the target is ambiguous, it asks before installing anything.

How are authentication fixtures handled in browser tests?▼

Auth support is added only when the real login route, session contract, and credential sources are discoverable in the repository. It never generates helpers from guessed selectors, stores browser state only in ignored paths, and reports missing inputs when the contract is unknown.

Will it commit changes or add secrets to CI?▼

No. The Skill only writes local files such as configuration, tests, CI workflows, and documentation. It never commits, pushes, creates pull requests, or writes secret values, and it adds schedules or third-party CI integrations only when explicitly required.