run-e2e

Run Playwright end-to-end tests across multiple browsers.

1|Updated Mar 18, 2026
One-click install
npx skills add https://github.com/furrycolombia-sys/candyshop --skill run-e2e-furrycolombia-sys
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: run-e2e
Source: https://github.com/furrycolombia-sys/candyshop/tree/main/.agents/skills/run-e2e
Command: npx skills add https://github.com/furrycolombia-sys/candyshop --skill run-e2e-furrycolombia-sys

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates running end-to-end Playwright tests across multiple browsers and test files, reducing manual test orchestration and speeding releases.

Core Features & Use Cases

  • Run all Playwright tests across configured browsers.
  • Run specific test files or suites for targeted verification.
  • Switch between UI mode and headless execution to match your debugging needs.
  • Follow the Claude workflow as the canonical source for test execution.

Quick Start

Run a full Playwright end-to-end test pass using the default Claude workflow as the canonical source.

Frequently Asked Questions about run-e2e

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

FAQPage Schema
How do I run Playwright E2E tests across multiple browsers automatically?

You can run Playwright E2E tests across multiple browsers automatically by applying a Claude-based workflow that orchestrates test execution for all configured browsers, reducing manual test orchestration and speeding up releases.

Can I run specific Playwright test files instead of the entire suite?

Yes, you can run specific Playwright test files or suites for targeted verification, allowing you to isolate UI checks to individual files rather than executing the full test suite across all browsers.

Does this workflow support Playwright UI mode for debugging end-to-end tests?

The workflow supports switching between Playwright UI mode and headless execution, allowing you to match the test environment to your debugging needs during end-to-end test verification.

What is the canonical source for configuring end-to-end test execution in this workflow?

The canonical source for configuring end-to-end test execution is the Claude workflow defined in .claude/skills/run-e2e/SKILL.md, which dictates how test selection and multi-browser operations are applied.

Do I need any external dependencies to automate cross-browser E2E testing with Playwright?

No external dependencies are required to automate cross-browser E2E testing; the workflow relies solely on the internal Claude-based configuration and Playwright's built-in multi-browser capabilities to execute tests.