playwright-automation

Designs TypeScript Playwright test suites with locators, fixtures, authentication, and CI-ready configuration.

2|Updated Apr 18, 2021
One-click install
npx skills add https://github.com/rabbicse/go-projects --skill playwright-automation-rabbicse
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: playwright-automation
Source: https://github.com/rabbicse/go-projects/tree/main/projects/movie-ticket-booking/.claude/skills/playwright-automation
Command: npx skills add https://github.com/rabbicse/go-projects --skill playwright-automation-rabbicse

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you produce stable, maintainable Playwright end-to-end tests instead of brittle suites that flake on waits, CSS selectors, and shared state.

Core Features & Use Cases

  • Production-grade TypeScript Playwright patterns with page objects, component objects, and fixture-based setup.
  • Safe test authoring with user-facing locators, web-first assertions, storageState authentication, API mocking, and parallel execution.
  • CI-ready guidance for browser matrices, sharding, retries, tracing, screenshots, and debugging.
  • Ideal for greenfield E2E suites, Cypress or Selenium migrations, flaky-test reduction, and multi-site or multi-role applications.

Quick Start

Ask the assistant to create a TypeScript Playwright test suite for your app using role-based locators, fixtures, authentication state, and CI-ready configuration.

Frequently Asked Questions about playwright-automation

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

FAQPage Schema
How do I create stable Playwright tests that don't flake on waits and CSS selectors?

Migrate Cypress or Selenium tests to Playwright by adopting TypeScript-first locators, web-first auto-waiting assertions, and fixture-based setup. This Skill provides production-grade patterns to transition your E2E suites into stable, maintainable Playwright tests with CI-ready reporting.

How do I handle authentication in Playwright tests across multiple user roles?

Handle Playwright authentication across roles using storageState-based fixtures. This method captures and injects authentication states, enabling fixture-driven isolation for multi-role or multi-site applications without repeating login workflows in every test.

What's the best way to configure multi-browser Playwright runs in CI?

Configure multi-browser Playwright CI runs by applying browser matrices, sharding, and retries. This Skill guides setting up parallel execution, tracing, screenshots, and CI-ready reporting to optimize E2E test workflows and debugging across different environments.

Why should I use the Page Object Model with Playwright and TypeScript?

Use the Page Object Model with Playwright to encapsulate component objects and user-facing locators, ensuring test suites remain maintainable during refactors. This pattern pairs with TypeScript-first authoring and fixture-based setup to isolate test state and reduce flakiness.

Does Playwright support API mocking and network interception for E2E tests?

Playwright supports API mocking and network interception to isolate E2E tests from backend dependencies. Combined with fixture-driven isolation and web-first assertions, you can safely mock API responses to test edge cases and UI states without requiring live server data.