playwright

Automate browser testing and end-to-end UI verification with Playwright.

2|Updated Apr 6, 2026
One-click install
npx skills add https://github.com/bingeli1379/eli-claude-marketplace --skill playwright-bingeli1379
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: playwright
Source: https://github.com/bingeli1379/eli-claude-marketplace/tree/main/plugins/eureka-sdd/skills/playwright
Command: npx skills add https://github.com/bingeli1379/eli-claude-marketplace --skill playwright-bingeli1379

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Automates browser testing and end-to-end UI verification across modern browsers, reducing manual QA effort and speeding release cycles.

Core Features & Use Cases

  • Auto-detect dev servers and choose the correct test target across localhost or remote URLs.
  • Write and run Playwright-based tests using a consistent workflow via a run.js wrapper.
  • Use visible browser by default and parameterize base URLs for flexible testing across environments.
  • Supports cross-browser patterns, test organization, and quick-start setup for teams adopting Playwright.

Quick Start

Navigate to the skill directory and run the setup script to install Playwright and initialize the environment.

Frequently Asked Questions about playwright

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

FAQPage Schema
How do I automate browser tests to run across multiple modern browsers?

Automate browser tests across modern browsers by writing end-to-end UI verification scripts. The workflow uses a consistent run.js wrapper to execute Playwright tests, automatically detecting dev servers and parameterizing base URLs for flexible cross-browser testing environments.

Can I run cross-browser tests against a specific localhost or remote dev server?

Yes, cross-browser tests can target specific dev servers. The automation auto-detects running dev servers and selects the correct test target across localhost or remote URLs, parameterizing the base URL to ensure UI interaction automation hits the intended environment.

How do I set up Playwright for end-to-end web testing?

Set up Playwright for end-to-end web testing by navigating to the skill directory and running the setup script. This installs Playwright and initializes the environment, writing tests to a temporary directory and utilizing a run.js wrapper for consistent test execution.

Does end-to-end UI testing support visible browser mode by default for debugging?

Yes, end-to-end UI testing uses a visible browser by default for debugging and verification. This setup supports cross-browser patterns and visual regression checks, allowing teams adopting Playwright to quickly start automating web tests with visible feedback.

What are the limitations of running web tests written to a temporary directory?

Web tests written to a temporary directory require Playwright setup and a run.js wrapper for execution. A known limitation is that the environment must have auto-detection of running dev servers configured properly, otherwise the test automation may fail to select the correct test target.