write-playwright-e2e

Implement Page Object Models and web-first assertions for Playwright end-to-end tests.

9|3|Updated Jun 13, 2026
One-click install
npx skills add https://github.com/Sir-chawakorn/sanook-cli --skill write-playwright-e2e-sir-chawakorn
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: write-playwright-e2e
Source: https://github.com/Sir-chawakorn/sanook-cli/tree/main/skills/write-playwright-e2e
Command: npx skills add https://github.com/Sir-chawakorn/sanook-cli --skill write-playwright-e2e-sir-chawakorn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill addresses the common pain points of brittle, flaky, and slow end-to-end browser tests by enforcing industry-standard patterns for reliability and maintainability.

Core Features & Use Cases

  • Reliability Engineering: Implements auto-waiting and web-first assertions to eliminate manual sleeps and race conditions.
  • Scalable Architecture: Promotes the Page Object Model (POM) to keep selectors centralized and tests readable.
  • Use Case: When a critical user flow like a checkout process is failing intermittently in CI, use this Skill to refactor the test suite, implement network mocking, and establish a stable, cross-browser testing strategy.

Quick Start

Use the write-playwright-e2e skill to bootstrap a new test suite and refactor existing flaky browser tests into stable Page Object Model scenarios.

Frequently Asked Questions about write-playwright-e2e

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?

To fix flaky Playwright E2E tests, refactor them using web-first assertions and auto-waiting to eliminate manual sleeps and race conditions, ensuring deterministic execution across browsers.

What is the Page Object Model pattern for web testing automation?

The Page Object Model centralizes UI selectors and test logic, keeping browser-based test suites readable and maintainable while stabilizing critical user flows like checkout processes.

How to set up cross-browser validation with Playwright?

Cross-browser validation requires configuring the Playwright test framework to execute scenarios across different browsers, applying network mocking and visual regression checks to ensure broad compatibility.

Can I use network mocking to isolate critical user flows in E2E testing?

Yes, network mocking isolates critical user flows in E2E testing by intercepting external dependencies, which stabilizes test execution and enables reliable failure forensics during CI runs.

Does Playwright support visual regression testing for browser-based applications?

Playwright supports visual regression testing by capturing and comparing browser rendering snapshots, helping detect unintended UI shifts during automated end-to-end validation scenarios.

Why does my Playwright test suite fail intermittently without manual sleeps?

Intermittent Playwright test failures occur when tests lack web-first assertions and auto-waiting, causing race conditions; refactoring to enforce deterministic execution resolves these timing issues.