playwright-expert

Create Playwright end-to-end browser tests with Page Object Model patterns.

Updated Mar 17, 2026
One-click install
npx skills add https://github.com/Estom/aiflex --skill playwright-expert-estom
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: playwright-expert
Source: https://github.com/Estom/aiflex/tree/main/skills-repo/Jeffallan-skills/playwright-expert
Command: npx skills add https://github.com/Estom/aiflex --skill playwright-expert-estom

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

End-to-end browser tests are often brittle, slow, and flaky; this Skill helps design reliable, maintainable Playwright test suites that reduce flakiness, speed debugging, and integrate smoothly into CI pipelines.

Core Features & Use Cases

  • Test Architecture & POM: Guidance for Page Object Model patterns, component page objects, and fixture composition to keep tests maintainable.
  • API Mocking & Isolation: Route interception patterns and HAR-based playback to isolate UI tests from backend variability.
  • Debugging & Resilience: Instructions for traces, screenshots, retry strategies, and anti-flakiness patterns to diagnose and fix intermittent failures.
  • CI Integration & Configuration: Recommended playwright.config settings, reporters, retries, and webServer setups for reproducible CI runs.
  • Use Case: Implement a login Page Object, mock authentication responses, and run cross-browser tests with trace capture on failures to ensure stable releases.

Quick Start

Create a Page Object for the login flow, write a Playwright test that mocks the login API, enable trace retention on failure, and run the suite in CI.

Frequently Asked Questions about playwright-expert

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

FAQPage Schema
How do I fix flaky Playwright E2E tests in my CI pipeline?

Fix flaky E2E tests by capturing traces and screenshots on failure, applying retry strategies in your playwright.config, and mocking API routes to isolate UI tests from backend variability.

What is the best way to structure maintainable Playwright test suites?

The best way to structure maintainable Playwright tests is using the Page Object Model pattern. This Skill provides guidance on component page objects and fixture composition to keep your test architecture clean and maintainable.

How do I mock API responses in Playwright to isolate browser tests?

Mock API responses in Playwright by using route interception patterns and HAR-based playback. This isolates your E2E browser tests from backend variability and ensures consistent, reliable test execution.

Can I configure Playwright for parallel cross-browser testing in CI/CD?

Yes, you can configure Playwright for parallel cross-browser testing in CI/CD. This Skill provides recommended playwright.config settings, reporters, webServer setups, and retry strategies for reproducible CI runs.

Does Playwright support visual regression checks and trace capture for debugging?

Yes, Playwright supports visual regression checks and trace capture for debugging. You can enable trace retention on failure to diagnose test issues quickly and ensure stable application releases.