skills.rest
jeff-hamm
jeff-hammCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

playwright

Run Playwright e2e tests in headed mode with optional debugging flags.

Updated Aug 23, 2026
Search Tags:#automation#testing#debugging#e2e#playwright#headed#chromium
One-click install
npx skills add https://github.com/jeff-hamm/ai-tools --skill playwright-jeff-hamm
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: playwright
Source: https://github.com/jeff-hamm/ai-tools/tree/main/src/skills/playwright
Command: npx skills add https://github.com/jeff-hamm/ai-tools --skill playwright-jeff-hamm

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Running Playwright e2e tests in a visible browser to observe interactions, catch UI issues, and debug flows without headless mode.

Core Features & Use Cases

  • Run tests under tests/e2e in headed mode with --workers=1 and --project=chromium.
  • Support single spec or grep-based targets, with optional slow-mo and debugging via environment variables PWDEBUG and PWSLOWMO.
  • Ideal for demos and step-through debugging with Inspector.

Quick Start

From the repository root, run a headed Playwright test against tests/e2e with a single spec or grep pattern using npx playwright test <spec> --headed --workers=1 --project=chromium, optionally setting PWSLOWMO or PWDEBUG=1 for slow motion or debugging.

Frequently Asked Questions about playwright

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

FAQPage Schema
How do I run Playwright e2e tests in a visible browser?▼

Run Playwright e2e tests in a visible browser by executing specs under tests/e2e with --headed, --workers=1, and --project=chromium flags to observe interactions and catch UI issues without headless mode.

Can I debug Playwright tests with the Inspector?▼

Debug Playwright tests with the Inspector by setting the PWDEBUG=1 environment variable, which enables step-through debugging for your headed e2e test execution.

What is the best way to slow down Playwright test execution for demos?▼

Slow down Playwright test execution for demos by setting the PWSLOWMO environment variable, which applies a delay to headed test runs for easier observation of UI interactions.

Do I need Node.js installed to run headed Playwright tests?▼

Node.js and Playwright installed are required to execute headed e2e tests, as the automation relies on npx playwright test commands and local browser projects.

How do I run a single spec file in Playwright headed mode?▼

Run a single spec file in Playwright headed mode by passing the spec path to npx playwright test along with --headed, --workers=1, and --project=chromium execution flags.

Why run Playwright tests with only a single worker?▼

Running Playwright tests with --workers=1 in headed mode ensures browser interactions remain visible and manageable, preventing multiple visible windows from overlapping during execution.

Related Skills

Explore More Software Engineering Skills→
ryankoleanryankolean
3

cli-playwright

Automate browser interactions and end-to-end tests across Chromium, Firefox, and WebKit.

Community
Advanced
txema-puchtxema-puch
1

browse

Drive a headless browser to automate QA testing against arbitrary URLs.

Community
Advanced
act70255act70255

gitlab-ci-patterns

Automate GitLab CI/CD pipeline configuration with multi-stage workflows and caching.

Community
Advanced
betaTridentbetaTrident

browser-qa

Automate visual regression testing and UI interaction verification for web applications.

Community
Advanced